nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Best practice for letting developers specify a resolution without resolving an issue

Danielle Zhu1

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?

Accepted answers

Nic Brough -Adaptavist-

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.

All comments

Jobin Kuruvilla [Adaptavist]

Sounds like a good approach. Can't think of anything else to beat it!

Danielle Zhu1

Thanks, Jobin and Nic, for validating the idea!

Nic Brough -Adaptavist-

Yeah, that's not going to work - the definition of "resolved" in Jira is "has a resolution"

Joe Pitt

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.

Danielle Zhu1

Interesting we were just discussing whether to call it Dev Resolution or Initial Resolution.

Nic Brough -Adaptavist-

I prefer something along the lines of "developer's resolution" because that makes it clear who is making that decision.