Jira workflow with Portfolio as it relates to the Resolution field

Debbie Weinstein April 15, 2019

I recently learned that Portfolio for Jira will only bring in tickets that have a Resolution of UNRESOLVED. 

We have been using Jira for a number of years and our workflow is such that an open ticket flows from Product Managers to Developers to QA who ultimately close the ticket.

When the developer fixes the issue they Resolve the jira and then QA tests Resolved issues. Changing the Status to Resolved also changes the value of Resolution and therefore those Resolved issues, that aren't done but still in QA are not being pulled into the timeline in Portfolio as Portfolio now considers the tickets DONE (because Resolution is no longer UNRESOLVED).

I'm looking for Best Practices for Workflow for those of you who have  a similar way of using jira (jiras flow form one group to another and aren't considered DONE until all are finished).  And if you're using Portfolio as well, even better!


1 answer

0 votes
Žilvinas Bartkus
I'm New Here
I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
April 28, 2024

Some years after, but I also have the very same question on Resolution status. Where should we resolve the ticket:

  • Developer?
  • QA?

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events