How to prevent automated sections in whiteboards from executing the action on each page load ?

[Andrei Eleodor Sirbu]

Hello community, 

We have identified a problem so I'm posting here first in case someone has a workaround. 

We have whiteboards with automated sections which we use for specific ceremonies. Teams use them to quickly place their stories in the right section, which then automatically assigns the story to a sprint. It all works like a charm. 

Now let's say we place issue A in an automated section which applies Sprint A to that issue. 

Three weeks later, the team moves that issue from Sprint A to sprint B (through the backlog view in Jira)

Whenever we open the whiteboard, it loads the sections first, then the Jira issues which acts as a manual operation and executes the automation. The result is that the story will move back to its previous sprint. 

So unless we cut the automations at the end of our ceremony, or block access to the whiteboard so nobody loads it anymore I didn't find a way to prevent this from happening. 

Kind regards

Andrei 

[Hans Polder]

Hi @Andrei Eleodor Sirbu ,

Apologies for my previous comment - I had multiple tabs open and was intending to close another duplicate post ;)

With regards to your post: Thanks for detailing your case so much! This should be reproducible, however I can imagine that taking some time. I've asked someone from Atlassian Support to take a look at this case, as it seems like a bug or at least undesired/unexpected behavior!

[Andrei Eleodor Sirbu]

Hello @Hans Polder  , thank you for raising the issue to your team. 

If you'll find it hard to reproduce your team might want to try with a larger volume of issues (50+) scattered acccross different automated sections. 

Have a great day 

Andrei 

[Dhanush]

Hi @Andrei Eleodor Sirbu ,  I created a support ticket for our Technical Support team to assist you. You will soon hear back from our team with the ticket number!

[Andrei Eleodor Sirbu]

Hi Dhanush, thank you I've received a response already :)

We're following the issue with the technical team. 

Kind regards

Andrei