Feature #3193
open
Provide more context for issue statuses
Added by Anonymous over 15 years ago.
Updated over 11 years ago.
Description
An article popped up in my RSS feeds today about a new issue tracker called DoneDone. One feature it provides is more context around issue statuses. Rather than try and describe this myself, it would be easier to look at http://www.wearemammoth.com/sprout/2009/04/when-it-comes-to-issues-looks-do-matter.html. You can also see this on the official site in the second point on http://www.getdonedone.com/features.aspx, the one about Issue Statuses.
I think this style of user interaction would be an excellent to bring to Redmine, making it more natural for users to push issues back and forth without needing to scroll up/down through heaps of comments to find why they've been assigned the issue.
I have no idea this sort of extension is possible with the existing plug-in architecture.
Files
+1 Love this.
We in the development team LOVE Redmine but it can be hard to convince some of our business users to feel the same way. I think this type of approach would go a long way towards it.
Link are broken. But would like to understand more if explained here itself.
Well as we are not able to understand the concrete idea please give feedback until next month. Otherwise this will be closed. Which would be sad.
I checked the homepage for myself and couldn't find any feature regarding different issue status functions.
- Due date set to 2013-04-18
- Status changed from New to Needs feedback
That's annoying that the links have broken, but I guess it has been 4 years.
So the idea is to add more context about the transitions between statuses. Both Jira and Mingle do this by allowing labels to be added to status transitions (Redmine only allows you to say if something can or can't move from A to B). The following screenshot is from Jira and shows an issue that is in "Backlog" with transitions available to "Defined" or "In Progress". The key though is that they allow the user to label these transitions which are then shown as actions:
This makes it a lot easier for people to understand what they can do with an issue, and makes it a lot faster to use to. For example, an action at the top labelled "Ready for testing" rather than having to click "Edit", then find the status drop-down, then look to find the "Testing" status.
If I understand it right here are following takeaways
- There should be (nice) "Buttons" that jumps to specific direct actions as opposed to "Update"
- These buttons can be many actions "New issue", "In progress"/ "Diagnosis", "Respond to Author", "Respond to assignee" etc.
- The change of state can be one of those Action Buttons.
- An obvious implication would be that only actions which are permitted to me based on workflow possibility and role permissions, should be shown.
Also, we need to define as to where to keep these buttons. An obvious advantage of having such buttons is that they don't occupy space on the Menu bar.
This is no functionality change, but might make UI attractive and intutive. Good to have this though!
By the way, there exists a plugin Issue Hot Buttons which achieves some of this. Unfortunately this isn't yet ported to latest Redmine!
Yes - that plugin is close, but I would imagine that they would simply open the usual "Update" panel but with the status modified. This allows for a consistent UI, with the ability to add comments, etc..
Mischa The Evil wrote:
There also exists an other, older plugin which allows quick changing of the issue status: PluginSidebarIssueControl (Sidebar Issue Control ).
This sounds interesting - unfortunately, the plugin is quite outdated.
- Due date deleted (
2013-04-18)
Maybe I could find a way to solve this or give another approach. :-)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by 
Updated by