Atlassian VS Code JQL queries

Question

Installed Atlassian for VS Code and it's working well apart from one issue.

The initial query displays all my issues, including unresolved closed subtasks. A couple of us have tried to get rid of these unresolved closed items through JQL, but it is very stubborn and still shows up;

assignee = currentUser() and resolution = Unresolved and statusCategory != Done

Any suggestions peeps?

Nic Brough -Adaptavist- · Answer

The out-of-the-box workflow works with "assignee = currentUser() and resolution is empty", so I'm a bit stuck on what is wrong here if you're using it.

Greig Strafford · Answer

I think it's because it's the out of the box workflow on stories. I haven't tweaked it yet as it's only been a week and the bugs workflow is where the magic is happening. I think it's just the sub-task's finicky manner, it'll just me easier for me to shove in a decent workflow.

Thanks Nic,  I look forward to the community article ;)

Nic Brough -Adaptavist- · Answer

The "done" status may or may not contain unresolved issues.

In Jira, Done, Resolved and the StatusCategory have an uneasy and complicated relationship which can be very inconsistent.

Given a few minutes I could configure a Jira that allows me to have an issue that is "Unresolved", "in Progress", "to-do" and "Done" all at the same time.  Most of us desperately try to avoid that by setting up consistent workflows and config.

I think the question here comes down to how you've got your flows set up and what VS Code really needs to see from it.  I think we need to see the workflow for the issues you are looking at in VS Code - could you screenshot that?

(For those landing here and questioning the double-quantum state - the issue has no resolution set, the status is "in progress", and I've put the status "in progress" in the "to do" status category, and mapped it into the "Done" column in my board.  I feel a community article coming on)