Stream: JIRA/Confluence
Topic: Waiting for Input
Lloyd McKenzie (Nov 18 2019 at 11:12):
One of the new few features of Jira is that it sends out a weekly email of any issues that have your user account associated with the issue as "waiting for input". Once you log into Jira, you can select the workflow option "provide input" which will let you provide a comment and will automatically transition the issue back to 'Triaged'. (If you just provide a comment and don't click the 'provide input' link, the status will remain 'waiting for input' and you'll continue to get weekly reminders.
Also note that waiting-for-input can only be tied to one assignee at a time and must be a registered Jira user.
Grahame Grieve (Nov 18 2019 at 11:13):
log in to Jira...
Lloyd McKenzie (Nov 18 2019 at 11:17):
:) Fixed. It's going to take a while for the neurons in my head to get appropriately re-wired... (Speaking of wiring, in the minutes for my last scouts meeting, I noted that we're going to practice with FHIR extinguishers :>)
Lloyd McKenzie (Nov 21 2019 at 20:20):
The transition to "Waiting for Input" when assigning an 'open' issue is by design. The only reason to assign unresolved items to an individual is to solicit input. Assigning an item once it's been closed will not transition to waiting for input
Lloyd McKenzie (Nov 21 2019 at 20:22):
@Sean McIlvenna
Sean McIlvenna (Nov 21 2019 at 21:17):
so, I assigned a "Triaged" issue to a member of the workgroup, knowing that they would need to propose a resolution
Sean McIlvenna (Nov 21 2019 at 21:17):
when I assigned the "Triaged" issue to someone, it transitioned it automatically to "Waiting for input"
Sean McIlvenna (Nov 21 2019 at 21:17):
I would think it should stay "triaged"...
Jean Duteau (Nov 21 2019 at 21:20):
I had this same confusing problem on Monday. I thought I had done something wrong because all I did was add a comment and assign the issue to myself. It automatically went to "Waiting for Input" when I expected it to stay at Triaged. I believe (although I may be confused) that a Resolved issue also moved to Waiting for Input when I assigned it to Melva to do the work.
Lloyd McKenzie (Nov 21 2019 at 22:19):
If they need to propose the resolution, then the item is waiting on input from that individual. They will receive weekly email reminders of their need for action (whatever it is). As soon as they indicate that feedback has been provided (in this case, a proposed resolution), the item will return to triaged, meaning it's ready for work group (rather than individual) action/review.
Lloyd McKenzie (Nov 21 2019 at 22:20):
Any item that has a status of "Resolved - Change required" that is assigned to someone should not change the status. (If this happens, please holler). No other resolved status should allow assigning an assignee.
Lloyd McKenzie (Nov 21 2019 at 22:20):
@Jean Duteau What was the reason for assigning the unresolved issue to yourself?
Jean Duteau (Nov 21 2019 at 22:24):
is it possible to see the edit history of an item? I know the two items that I saw this on, but I can't remember the sequence of what I was doing (to see if I did something wrong or not)
Lloyd McKenzie (Nov 21 2019 at 22:27):
There's a history tab at the bottom
Lloyd McKenzie (Nov 21 2019 at 22:28):
(Alternate tab with 'comments')
Last updated: Apr 12 2022 at 19:14 UTC
