Why do many Jira Workflows not set Resolution while Jira Assumes this field Defines Open/Done?

[James P. Hilving]

Many queries, like the system "My Open Isuses", assumes that the Resolution = Unresolved is the key to seeing if an issue is completed or not.

Jira now has some very handy Project Templates and Workflows that offer many out of the box solutions. The problem I am seeing is how many just do not set a resolution? Even the "Typical Software Development" workflow does not set the resolution.

This makes queries that rely on the resolution field useless. In this case I have no way to remove the "Done" Issues from my "Open Isuses" Filter.

So while I know that I can fix this in the workflow...why is the system and the "common" workflows not matching up? Just adding 'AND status != Done' would actually make a lot of these workflows work without needing extra modifications.

[James P. Hilving]

Yes I agree...a post function (for Done) would be ideal.

[Sameera Shaakunthala [inactive]]

Just adding 'AND status != Done' is not the way to go. Actually a workflow post function should be created so that JIRA will automatically set the issue Resolution.

I think Atlassian might need to look at this as a future improvement.

[James P. Hilving]

We are currently on v6.1.1.

[Sameera Shaakunthala [inactive]]

What's the version of your JIRA?