Hi!
In one of our teams it regulary happens that there are multipe issue (about 5-10) that should be unified to just one ticket. This is necessary because the team has to work with the single issue but the also need a new issue which refers to all single issues.
It´s like having 3 different issue called "apple", "orange" and "banana" and I want to unify them to a new "fruits" ticket.
It would be nice to have the opposite of the "split issue" function.
I already thought about creating manually a new ticket and linking all the other issues to the new one. But in this case all the information still would be spread to every single ticket.
So, is there a better way?
Thank you.
Greetings
Simon
Hi Allison,
I have spent some time looking into the standard JIRA reports, and it is certainly not obvious as to what they do.
I have created sample reports for Intelligent Reports that follow the User and Version workload reports as closely as possible, but have not looked at the time tracking report.
Generally they seem to follow JQL queries along the lines of:
assignee={User} and resolved is EMPTY and (timespent > 0 or originalEstimate > 0)
and use timeSpent + remainingEstimate instead of originalEstimate.
Cheers,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.