-
Notifications
You must be signed in to change notification settings - Fork 460
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
Feature request: show issue priority on backlog page #997
Comments
I'm not quite sure how this should work but we want to be able to manage user stories by must/should/could have and seeing this on the backlogs page would be really helpful. I'm not sure how that impacts the drag behavior of the user stories in the backlog but a good start would simply to see the priority of those items displayed. |
I have a similar feature request for seeing something on backlog page - my wish is to see issue category on backlog page. I would broaden the original FR to read 'Select issue parameters so show on backlog page' - to avoid situation where the original FR is implemented and next user enters FR for showing e.g. issue assignee in backlogs. Currently the v1.0.6 configuration has selection 'Show project name in backlogs' This could e.g. be changed to multi-select dropdown similarily to 'Story trackers', and user could select from a list of possible parameters those parameters to show. Naturally, UI implementation should take into accountreadability issues etc. I'm not a developer myself, so I can't help in implementing the feature, sorry. |
This is not a very elegant way to do this, but I added priority to the backlogs with:
And here's some CSS to help clarify things a bit
|
Currently the issue priority field isn't visible on the backlog page, either on the list or in the popup when hovering on an issue number.
Changing the colour of the entries would be a subtle way of adding it, perhaps using the tracker colour on one part of the row and a priority colour on another? Else at least showing the field in the popup would be very useful.
The text was updated successfully, but these errors were encountered: