Using Software Dev workflow - resolution field

[Jane Scolieri]

We have made the resolution field editable so people can adjust when editing a bug/issue. But these issues don't show up when searching for Open bugs.

The Software dev workflow seems most appropriate for us, as we are mostly waterfall. Any suggestions? Perhaps we set up the Statuses wrong? Not sure we really grasp that and the Transitions. Just need help with the settings, don't really want to go too deeply into workflows.

[Nic Brough -Adaptavist-]

Short answer - remove the resolution field from your edit screen. It's wrong.

You've done nothing wrong with status or transitions, it's just resolution.

If you put the Resolution field on any edit screen (create, edit or transition), then it will be set when the user commits their change. Doesn't matter if they don't touch it - it's defaulted and there is no "none" option. That makes your issues appear closed as far as Jira is concerned. You need to stop doing that immediately.

Technically, there is little reason to be editing resolutions - they should only apply to issues at the end of their lifecycle, where they actually don't really matter too much because you've dealt with them.

In the odd cases where you do want to edit a resolution, add a looped transition (i.e. from Closed to Closed) that goes through a transition screen that does include the field.