Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Issue with linked issues

sprasad January 19, 2023

Is there any known issue with displaying linked issues. It seems "blocks" relationship is reversed

1 answer

0 votes
Trudy Claspill
Community Champion
January 19, 2023

Hello @sprasad 

Why do you think the "blocks" relationship is reversed?

Why do you suspect there is a problem with displaying linked issues?

Please provide screen images and detail what you think is wrong in them.

sprasad January 19, 2023

History shows correct blocked relationship.  HAR 2008 is blocked by HAR-2245.

 

HAR-2008 Linked Issues SectionHAR-2008 History.jpgHAR-2008 Linked Issues.jpgHAR-2245.jpg

Trudy Claspill
Community Champion
January 20, 2023

Hello @sprasad 

Thank you for that additional information.

Can you look through the older history entries on HAR-2245 and see if you find one for "This issue is blocked by HAR-2008"?

The only way I was able to recreate a situation like this was to (using your Issue IDs in my next statements):

1. In HAR-2008 create a "blocks" link to HAR-2245.

2. In HAR-2008 create an "is blocked by" link to HAR-2245.

(At this point there are two links between the two issues, so that each appears to be blocking the other.)

3. In HAR-2008 delete the link that says HAR-2008 is blocked by HAR-2245.

In the history there is still an entry for when link #2 was created, even though that link no longer exists. And there is no history entry for the removal of that link.

Luke Towers
Contributor
April 5, 2023

Hi @sprasad & @Trudy Claspill 

Did you make any further progress on this issue? 

We have the same thing happening on various Jira issues. I have tested and cannot replicate from my side. 

History on the ticket shows that it was linked as "is blocked by" but when you look at the linked issues field it shows the reverse "blocks" 

Thanks 

Trudy Claspill
Community Champion
April 5, 2023

@Luke Towers  @sprasad 

There was another thread discussing this issue where, in that case, it was determined that it was being caused by a bug in a third party app - BigPicture v8.11 from Appfire. Do you have that same third party app?

Luke Towers
Contributor
April 5, 2023

Thanks @Trudy Claspill We do not use BigPicture but we do use BigGantt from the same vendor. Assume that this is also the cause of our issue. I will add a comment on the other thread. Thanks so much

Suggest an answer

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

Atlassian Community Events