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
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Participate in fun challenges
Challenges come and go, but your rewards stay with you. Do more to earn more!
Gift kudos to your peers
What goes around comes around! Share the love by gifting kudos to your peers.
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!
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.
4,557,742
Community Members
Community Events
184
Community Groups
"blocks" changed to "blocked by" with nothing in history to explain it
Edited
Allan Pedersen
I'm New Here 
Mar 26, 2023 I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
Hi everyone.
I'm seeing a very strange behavior in Jira on multiple stories.
In these scenarios I have two seperate stories, one blocked by the other.
Story A -> Blocks -> Story B
Story B -> Is blocked by -> Story A
In the history log on both stories I can see how this is correctly placed the 14th of March.
But now they are reversed.
Here you see the actual story I'm in "10648" is blocked by "9037".
This is wrong.
Going into the history log, the only place 9037 is mentioned
is when it was correctly put as "blocks 9037, not blocked by it"
This is wrong.
Going into the history log, the only place 9037 is mentioned
is when it was correctly put as "blocks 9037, not blocked by it"
I also checked on 9037 and there the status is now also reversed.
And just to be clear I have gone through the history of both stories, line for line and neither automations or anyone manually changes the link between these stories.
is this a bug? I'm getting reports from developers that this is happening on multiple stories.
Even automations which I rarely use or bulk edits should be reflected in the history log, but nothing shows how this change happened, and I've just to be sure checked no automations are active that could have done this.
2 answers
Walter Buggenhout _ACA IT_
Community Leader 
Mar 26, 2023 Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Trudy Claspill
Community Leader
Mar 26, 2023 Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
Allan Pedersen
I'm New Here
Mar 27, 2023 I'm New Here
Those new to the Atlassian Community have posted less than three times. Give them a warm welcome!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.