Zephyr test status VS JIRA issue status

[Weijing]

I executed a test in Zephyr, but the issue status still was 'unresolved'. If I want to search all unresolved issues, I have to exclude Zephyr test issues.

How to make issue status as 'resolved' after a test was completed?

[Vinod Thomas]

My understanding is that a Test item is a test case and as such it should be marked finished once reviewed. However test executions are instances of a test case being executed in a test cycle. Its a bit confusing and I would welcome any suggestions.

[Frank Steudle]

This is my point of view: A test case is not PASS, FAIL or whatever. It is a document, which will be updated regularly. So it should be processed by using a JIRA workflow with simple states for creating and review (like mentioned here by Eddie). The default workflow for test executions should be enough, because there the states are PASS, FAIL,...

Best wishes

Frank

[Emily Schneider]

Hi Weijing,

Since an issue type Test is a standard JIRA issue type, the same rulesshould apply for it as a Bug, Task, Etc. You will need to add the issue type Test to your workflow and allow users to change the Test to closed/resolved as you do with other issue types. It is important to note that changing an issue type (any issue type including issue type Test) to Closed, or Fixed, or any JIRA resolution type is a JIRA feature. We in Zephyr for JIRA have no play in this. Because of this, if you are not sure how to allow an issue type to follow your current workflow, you will want to reach out to your JIRA admin or Atlassian, They will be able to assist you with your JIRA workflows and show you how to incorporate additional issue types into it.

Kind Regards,

Emily