Hello,
Below is our current process and I would like to work through how to incorporate this into JIRA:
How can the technician put in the request that a specific three people must say accept before the ticket can move on?
There's lots of options here, depending on your need!
Is this process implemented in Jira already? If yes, how do Steps 1/2 take place today?
What audit-level is needed for this? Is it...
If no acceptance is received, do you need to auto-notify those users? Should non-acceptance block an issue? Or does this not matter?
And where would you keep these 3 users? Is there a unique identifier which decides which user it is? Or would these users be in a custom user field?
If you have a view on these, it'd be great to hear to make a suggestion more specific :)
Ste
Hi Stephen,
Thanks for the quick response (and apologies for my delayed response).
This process is not implemented into JIRA, so it's a blank slate.
There will always be 3 user signoff requirements (sometimes up to 11), depending on the requested change.
It needs to be auditable (even if only by reviewing the comments). The main purpose is that the task cannot be pushed any further until all signoffs are complete.
Yes there should be reminder if the acceptance or rejection is not received within 2 days (and a reminder ever 2 days after that).
The users (for the time being) are manually chosen by our internal team. That being said, two users will always be the same. The originator must signoff on the request and our QC Manager will always be on it. Over time, I would like to implement automated practices to allow for auto assign, but that is version 2.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Ste Wright , I haven't heard back from you. Do you have any thoughts on how to accomplish the above?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.