I've got a request for workflow customization: allow developers to specify a resolution when they fix an issue but the issue needs to remain unresolved till QA verifies the fix and the documenation team update the documents.
I am thinking about creating a custom field that has the options of the Resolution field. It will be set by the developers. Then the real resolution field will be populated (copied from the custom field) when the issue is resolved in the end. What do you / would you do?
Yeah, that's not going to work - the definition of "resolved" in Jira is "has a resolution"
Your idea about creating a custom field and then using it to set the system-resolution later is exactly what I'd suggest though! Minimal coding, clear, automatically searchable and simple to explain to the users.
Sounds like a good approach. Can't think of anything else to beat it!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks, Jobin and Nic, for validating the idea!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
One place I worked I setup a 'Developer Resolution' field for the same reason. Until the fix is tested we didn't consider it actually resolved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Interesting we were just discussing whether to call it Dev Resolution or Initial Resolution. :)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I prefer something along the lines of "developer's resolution" because that makes it clear who is making that decision.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.