Issues closed/resolved by user
Added by Ruben Silva over 14 years ago
Hi,
I'm using Redmine for a while, and recently we have reached a substancial number of developers and we need to keep track of the issues being resolved by each one.
Our current workflow says that upon issue resolution the owner its changed to the issue tester, that after successful test closes the issue.
The problem here is that we lost track of the developer resolving the issue. The activity section gives a good vision of what each one does, but it's not pratical and displays to many info.
I wonder if there is a solution that i'm not aware or some kind of plugin that provides me this info. If not I strongly suggest extend and improve te user view section.
Thank you
Ruben
Replies (3)
RE: Issues closed/resolved by user - Added by Felix Schäfer over 14 years ago
I'm not sure to fully understand what you are looking for. Could you please rephrase the query and provide a little more information about your workflow?
RE: Issues closed/resolved by user - Added by Ruben Silva over 14 years ago
Sure I can Felix,
Flow:
1 NEW -> 2 ASSIGNED -> 3 RESOLVED (eventually) -> ... -> 4 CLOSED
1->2 Owner changes
2->3 Owner does not change
3->... Owner Changes
After issue resolution someone diferent than the developer is assigned to test the development, if the test is successful the issue is closed.
Now, I want to know the resolved issues by my developer. In the issue summary page we can see the info I want but it is not quite right. The closed issues by user filter the issues closed grouping by the issue author.
Do you see what I mean?
RE: Issues closed/resolved by user - Added by Felix Schäfer over 14 years ago
I think so, though I can't fathom a good way to get this sort of info out of redmine without extra data input. The simplest thing you could do is have a look at the user activity streams, i.e. go to the user page (for example mine) and click on the "Activity" header. Second idea: Make a custom field with the names of your devs, you can then use this custom field as a filter on the query view. Third idea: make your devs log time for a resolution and make the timelog categories for "issue solving" and "Q&A" disjoint.