Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Is there a way to block transtions for users during automation scripts execution?

Hi ladies and gentelmen!

I'am trying to set some automatic workflow and have some succes, but it may be broken by users in case of their "switch status" interference during scripts executions.

Is there a way to block transtions for users during automation scripts execution?

1 answer

Hi @Roman Zanevski 

If I understand your question, you want to prevent people from transitioning issues while automation workflow and rules are running.  Is that correct?

I expect the answer is "no".  Workflow and automation rules are event-triggered, and so a person transitioning an issue could trigger a rule, or during a very narrow window of time, conflict with the automation processing.

I recommend reviewing what you are doing with automation (workflow and rules), determine where impacts could occur, and adjust your automation accordingly.

Best regards,

Bill

Hi @Bill Sheboy

That's correct what I meant. I tried to adjust it, do independant scripts and had some succes too, but unfortunatly user still can use some limited time window to trigger another rule and what can affect to execution of current rule( Trying to find some solution now by using properties to restrict all groups exept automation jira app in case of rule's start

Thanks for explaining, Roman.  That is an interesting approach...  It seems you are describing checking the triggering user (or a property of them) to have the rule abandon processing in some cases.  Please post back here what you learn/decide to use.

One messy part of this use case is that once a rule is triggered and has the state of an issue, that context is used for rule execution.  If an issue's content changes *during* the rule execution it is not visible to the rule, and so could be replaced by the rule execution.  So even when a user does not trigger a rule through their actions, there can be data collision.  Using the re-fetch action can help, but it dramatically slows rule processing.

Suggest an answer

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

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