nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Are you able to change to status of a test issue

Chris Jeans

Are you able to change to status of a test issue? Attached are screenshots of a bug issue and a test issue. On the bug issue I am able to change the status (from open to in testing, in review, done) but with the test issue i cannot (only option is to execute test). I have created a workflow for test issues but I am unable to change it status from open to another status in the workflow (e.g. pending, closed, etc).

Would this be due to the fact that a test issue cannot have a different status and can only be executed but not closed? bug issue.PNG test issue.PNG

Accepted answers

All comments

Petter Gonçalves

Hello Chris,

This is the message sent on your previous question:

Checking your screenshots, I've further investigated it and found out that this "test" issue type is provided by the add-on Zephyr for JIRA and is not a native feature of JIRA Cloud.

I have installed the add-on and checked that test issue type have some additional functionalities, however, it works in the same way that other issue types of JIRA.

That been said, you can indeed edit the workflow applied to your test issue types and add any status you want by following the steps below. P.S: note that you must be an administrator on your project to perform such customizations:

- Navigate to your project > Project Settings > Workflows > Click to edit the workflow mapped for the test issue type

- customize your workflow as you want

Check in the screenshot below that I have shared the same workflow used to my native Issue types to the test and it is properly displaying the same workflow transitions to be performed:

Please, let me know if this information helps.

Chris Jeans

Hi Petterson,

Thank you for your response. I have a custom workflow assigned to these issues (attached screenshots). Is there an issue with the workflow that may be causing this?

Thanks,

Petter Gonçalves

Hello Chris,

I believe this is definitely a misconfiguration in your workflow. Can you please ensure there are no conditions/Properties blocking you to perform the initial transition of the workflow?

Also, make sure that your workflow transitions are properly configured and your workflow is already published and not displaying as a draft.

If you were not able to identify the problem, please send us a screenshot of your workflow and from your transition conditions/properties/validators configured on it.

We will be waiting for your answer.

Chris Jeans

Hi Petterson,

I have looked into the configuration previously but have not been able to find a source for the issue (I have tried setting statuses to have All statuses can transition to: ) as well as changing the settings within each. Screenshots attached are of the transitions in the workflow and the post functions on each (they all have the same post functions. Properties and Validators are 0 on all). post functions.PNG

Thanks,

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud

atl-gruland

marketplace