Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,463,777
Community Members
 
Community Events
176
Community Groups

Multiple Workflow statues visible when they should not be

Hello, 

Hoping someone can help here. 

We have a Jira board which has levels of approval set up, as its for Finance requests. 

User A will send in a cost req, it goes to their manager for approval- Status Requested-Approved. 

Once the manager has moved it to Approved it goes into Finance Approval. This queue is monitored by 2 people. 

The trigger for where the request goes next is based on a custom field and the status should be very specific. 

In the past week I have found regardless of the custom field, all statuses are visible causing some confusion.

The workflow a condition that only users in a specific group can see the status, and after some testing this is causing the issue. I wondered if there is another way around it.

To put the whole thing in context, only 2 people should have the ability to move tickets to the next stage which are Finance action (based on 2 custom field values) and 2nd Approval (based on 2 different custom field values). 

Hope all of this makes any sense. 

1 answer

1 accepted

0 votes
Answer accepted

This sounds like your conditions are not working, or there are alternate routes through the workflow.

Could you do a couple of things for us?  Find an issue that is showing this problem, and

1) Nip into the workflow diagram and give us a screenshot of it

2) Go to the project settings and find the workflow the issue type is using.  Can you show us what the conditions on a transition that should not be showing are?

@Nic Brough -Adaptavist- thank you for your reply. 

These are the conditions the same in both workflow statuses so only users in the group Pre-Approval should see the Finance Action step but only if the custom field equals any of the two categories. 

workflow conditions.png

The 2nd condition below is the same but the value categories are different.

workflow conditions2.png

What I am seeing now is anyone in the group can see both sets of status options regardless of the value category set. 

Hope that makes sense. 

Yes, it does, I think you've misunderstood how conditions work, and I'm not sure if your logic is flawed as a result!

Both your screenshots have the same problems, and there's three potential problems compounded.

Your first screenshot says (I'm shortening this a bit)

  • Any of the conditions
    • The field EVC will have to be equal to "£2500 to £5000", compared as a string
    • The field EVC will have to be equal to "Up to £2500", compared as a string
    • Only users in the group Pre-Approval

Problems

Is EVC a drop-down field?  With options of  "£2500 to £5000" and "Up to £2500", with those exact names? 

Which condition are you using for this comparison?  Is it "value field"?

And probably the main one - the "any" at the top means "or".  You're saying "let this happen if EVC = "£2500 to £5000" OR EVC = "Up to £2500" OR the user is in Pre-Approval group".  I suspect you want to swap that to "and", and try again.

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
PERMISSIONS LEVEL
Site Admin
TAGS

Atlassian Community Events