I have created a custom workflow (image attached).
When creating test issues i am unable to change the status and am only able to execute tests.
Is there a way to be able to progress there issues along?
We are running JIRA version v7.5.2
Thanks,
Chris
Hello Chris,
Welcome to Atlassian Community!
Could please let us know what you mean when you say "I can only execute tests"? Are you meaning the initial transition to TEST-EXECUTED that you configured in your workflow?
More specifically, can you please tell us what is the workflow transition that you are not being able to perform in your issues?
I would check the following configurations:
1 - Navigate to your Project settings > Workflows and check if your new custom workflow is properly configured for the issue-type you are trying to progress
2 - Navigate to your Project settings > Workflows > Edit > Click in the transition you are not being able to see/execute and check if there are any Conditions or Validators that could be blocking it.
3 - Make sure your workflow draft is properly published once you configured it
4 - Re-index your JIRA and perform an Integrity Checker in your workflow. P.S: Never run both re-indexing and Integrity checker tools at the same time. Also, depending on the size and traffic of your application, I would preferably perform it in a non-production time to avoid ay possible slowness in the system.
Please, let me know if it works for you.
Hi Patterson,
How would a re-indexing affect other projects on JIRA?
Thanks,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Chris,
There are two kinds of re-indexing methods:
- Background re-index
- Lock JIRA and rebuild index
You can check the documentation below to know the difference between the two options and how it would affect your projects:
Let me know if you still have any questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Petterson,
I have read through but I am unable to identify if either option will have any effect on our other JIRA projects. Can you please elaborate on this?
Thanks,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Chris,
The background Re-index could cause some slowness to your entire system, including other projects, however, it can be canceled at any time.
Locking down JIRA and rebuild index would turn-off your instance for some time, depending on its size.
Both activities would properly fix any incoherent behavior in your issues.
Additionally, you can optionally select a project level reindex, so it would be applied only for the project you select. To do this, navigate to your project > Project Settings > Click re-index project in the left menu.
Let me know if you still have any questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Patterson,
We will be trying this. On a side note if i create a test issue is it possible for the test issues to change status (like bug issues etc) from say open to closed? Or is this not available for test issues?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Chris,
Could you please let me know what do you mean by test issues?
If this is a different issue type in your instance, you can customize your project's workflow in a way that allows you to move it from Open to Closed, by creating a transition between both statuses.
For more information on Workflow customization, you can check the documentation below:
If you are talking about a different feature, please send me a screenshot displaying it in your JIRA view so we can further dig into this.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Petterson, i have further expanded on the status issue on this post https://community.atlassian.com/t5/Jira-questions/Are-you-able-to-change-to-status-of-a-test-issue/qaq-p/993151. You should understand from there what i mean by a test issue.
Thanks,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Chris,
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.