Imagine a situation where a ticket has been assigned, but the assignee is waiting for information (or whatever) from someone else on the team.
If a ticket is being blocked by a non-responsive team member, there ought to be a way to indicate that in one of the fields.
How do you normally handle this situation?
It really depends on your usecase and also the culture/process in your team. Different ways:
Option 1 tends to work best in my experience, although it is a bit of a faff for the admins as Renjith said. It makes it absolutely clear that the issue is blocked by waiting for input from a specific person and reporting on "issue can't be done becuase..." becomes really simple. Option 2 can be done with it of course, which helps with the involvement of many people, and there is absolutely no reason not to let other people contribute before they're needed as well.
It does depend on exactly how your organisation works though. Option 3 can be better for small teams and/or teams who work closely together because they will tend to talk to each other well. Option 1 is better for situations when the dependencies are outside the team using the project (e.g. we're writing a thingy, but we need input from corporate people about the UI). If you're using Jira to handle support work, option 1 is pretty much mandatory - you need at least one "waiting for feedback from user" type status.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs