In our organization we use Shared Configuration for project creation.
We have created around 26 projects with the same configuration (Say Project A to Z).
Now we wanted to restrict user from transiting from "To Do" state to "In Progress" state only when the tagged sprint is an active sprint for only few projects (say Project A, Project F, Project K, Project V).
Is there way to do this in JIRA datacenter version "Jira v9.2.0"
The option to achieve this is to have a JQL condition or validator within your workflow.
This will require an app to achieve this, app like;
These apps are providing additional functions to workflows, Ootb this can't be achieved in in Jira.
We tried using the JSU but its not working as expected.
1. It works for those projects mentioned in the condition but for those projects that are not mentioned in the condition are still restricted.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I don't think it's necessary to specify the projects you don't want to apply the condition to, You only create a condition for the matching projects.
If this still doesn't work, then make a copy of you workflow scheme and copy the workflow that applies to your issues.
Set the condition on that workflow and add this flow to the new workflow scheme.
Set this scheme on the projects that apply
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Karthikeyan Devi and thank you @Marc - Devoteam for mentioning us!
I am part of the Support Team of Decadis and I would be glad to share with you a possible solution with the Jira Workflow Toolbox Logical validator.
The following expression for the Logical validator would evaluate if the transitioned issue is in any of the stated projects and, only if it is, it would evaluate if it is in an active sprint. Issues from other projects will be transitioned.
%{issue.project.key} in [“PA”, "PF", “PK”] IMPLIES count(issuesFromJQL("key = "+ %{issue.key} +" and Sprint in openSprints () and Sprint not in futureSprints()"")) = 1
If you will test this configuration, please, replace the project keys “PA”, "PF", “PK” with the ones corresponding to the projects of your choice.
Some more use cases for our Logical validator can be found in our documentation.
Please, let us know if you need further assistance in this thread or via our Support Service Desk.
Best regards,
Vicente
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Vicente Domínguez _Decadis AG_ Thanks for your help but we are not in a situation to go for new plugin right now.
Problem with the current configuration is that it expects the user to have access to all projects mentioned in the condition. we are trying to contact the JSU Plugin support team.
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.