-
Notifications
You must be signed in to change notification settings - Fork 209
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Distinguish product and test issues bugref #708
Conversation
@@ -4,7 +4,7 @@ | |||
% if ($bug) { | |||
<span id="bug-<%= $jobid %>"> | |||
<a href="<%= bugurl_for $bug %>"> | |||
<i class="test-label label_bug fa fa-bug" title="Bug(s) referenced: <%= $bug %>"></i> | |||
<i class="test-label label_bug fa <%= $bug =~ /poo#/ ? 'fa-bolt' : 'fa-bug' %>" title="Bug(s) referenced: <%= $bug %>"></i> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggest to move that code into a helper
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will do, code update is not related. Need to rebase anyway, I guess
Progress is used to track test issues, bugzilla for product issues, at least for SUSE/openSUSE. This might be a lot different for other groups so a more flexible approach could be thought of but probably it is not as easy as just distinguishing on the issue tracker URL being used, e.g. if a group uses just one issue tracker but different components or issue types to differentiate, it is not that easy. That is why this simple solution is done here, first. At least others can follow the approach and have a test and CSS rule available ;-)
updated:
|
I prefer the lightning bolt than the upside down bug |
good, then nothing needs to be changed :-) |
Progress is used to track test issues, bugzilla for product issues, at least
for SUSE/openSUSE. This might be a lot different for other groups so a more
flexible approach could be thought of but probably it is not as easy as
just distinguishing on the issue tracker URL being used, e.g. if a group
uses just one issue tracker but different components or issue types to
differentiate, it is not that easy. That is why this simple solution is
done here, first. At least others can follow the approach and have a test
and CSS rule available ;-)
Example screenshot:
Alternative 1: Inverted bug icon, vote for this, if you like it more than what has been currently implemented: