The Atlassian Community Forums are currently in read-only mode. We will be relaunching on a new platform on September 22 (read more here). We apologize for the extended downtime. For concerns or questions, please email communitymanagers@atlassian.com. See you on the other side, on the new Atlassian Community Forums! :)

×

Forums

Articles
Create
cancel
Showing results forĀ 
Search instead forĀ 
Did you mean:Ā 

Can I block the possibility of switching from one status to another?

l.kubon
September 25, 2020

Hi

I created a workflow for projects in my company.

Is it possible to block or hide the possibility of using some transitions in the client project type?

As you can see on the screen, with TEST ON DEV we now have the opportunity to go to DEV ACCEPTED or directly to ACCEPTED.

I would like the project type client to only allow to switch from TEST ON DEV to DEV ACCEPTED. Transition accepted should be inactive or invisible

Is it possible? Without creating a separate workflow, NO PLUGINS. 

Zrzut ekranu 2020-09-25 o 14.36.31.png

3 answers

1 accepted

Comments for this post are closed

Community moderators have prevented the ability to post new answers.

0 votes
Answer accepted
l.kubon
October 2, 2020

I figure it out. I create custom field 'project category' and add value 'clients', then I associate to screens and choose only this where I wanna hide transmition. Then I edit default value - choose clients. 

Next I choose my workflow and click "edit", select trasmiotion and add conditions like on picture. 

Really it works :D 

Zrzut ekranu 2020-10-2 o 14.28.01.pngZrzut ekranu 2020-10-2 o 14.28.20.png

0 votes
Jack Brickey
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
September 25, 2020

Hi @l.kubon , sure this is possible. The solution depends on more info though. For example:

  • if you wish to never allow the transitions then edit the workflow and remove them. Note: if this is a shared workflow then you should make a copy of it, edit then associated to the specific project/issuetype.
  • if you wish to prevent the ability to transition under certain conditions, e.g. only the assignee, only if the value of a field has a value or certain value, etc., then consider adding a Condition to the transitions.

if you can provide more info I could assist further.

l.kubon
September 30, 2020

In my company we've got 5 different project category e.g intership, clients.... and one workflow. 

And I just thinking about this, it is possible to use this one workflow for different project category, but e.g. in clients project the transitom between  test on dev and accepted will be inactive. In another project e.g. transitom between test on dev and dev accepted will be inactive e.t.c. 

When transmiton will be inactive nobody in project should see this. Maybe there is some transition properties who can help>?

I don't know did I propper show you my conception. 

I don't want to create another workflow. I'm not a technical person and jira is new for me, so I don't know how limited are here. 

0 votes
Patricia Francezi_iDev_
Community Champion
September 25, 2020

@l.kubon 

In your scenario, do not show the transition, you must use a condition.

The condition will prevent the transition / status to be used

This will depend on how you apply the condition, and I do recommend you to read

https://confluence.atlassian.com/adminjiracloud/advanced-workflow-configuration-776636620.html

DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
AUG Leaders

Atlassian Community Events