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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Deleted automation rule still works

Hi, I've created an automation rule that enables only one user to change issue status from Backlog into To-Do. 
Since, it didn't work for us, I first disabled it - it still worked. Then I removed this rule from the list of Automation Rules, and it still applies for other project members that are not administrators. 
Not sure what happened and where to look for to disable this rule completely. Thought that disabling it and removing it would do the trick.

Can you please help? Thanks!

2 answers

0 votes
Guilhem Dupuy Community Leader Dec 09, 2020

Hi @Martyna Arent

If the Automation rule is Indeed responsible for this, disabling it should have been enough. You can maybe try Reindexing your jira instance ?

 

Let me know if it helped,

Guilhem

Hi Guilhem, thanks for the suggestion! I read about Reindexing here, and I don't see any message that suggest doing so - and I'd rather avoid it :)

Do you think there's another way to fix it?

 

Thanks!

Hi @Martyna Arent  -- Welcome to the Atlassian Community!

I wonder if a workflow change was made to block that transition.  Please check to see if there are any such rules on your workflow.


Best regards,

Bill

Hi Bill, thanks for the response!

Unfortunately - not. I didn't change anything in the workflow, it stayed the same.

It's a tough one :( 

Martyna

Hi!  Have you navigated to the site-admin level of automation rule management and looked at the audit log from there?  That may reveal what is causing this.  For example, a global scope rather than project scope rule.

And, if you look an a specific issue which has been impacted, who/what does it say made the change?

Suggest an answer

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

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

858 views 14 20
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you