Links hierarchy structure - the link type button does not save previous default

I was moving back and forth between 2 different issues. One the first level of one issue (called issue-1), only the "dependency" link type occurs and that is the only link type that shows up in the link type dropdown (it is selected). When I click on the arrows for the next level, 4 more link types show up. I don't care about those link types, so I unselect them.

Next I view another issue called issue-2. It has 2 different link types. I un-select one of them.

Now I go back to the previous issue. It only displays one level and again shows "dependency" link type as selected. When I click the level error and it finishes displaying level 2, the same 4 link types I had unselected when I previously viewed this issue how appear again as selected! I have the auto-save configuration button checked and expect those link types to be unselected as default from now on, but they are not.

This functionality is not working like it was back in the flash version of the plugin. I would like to see all possible link types in the link type dropdown, regardless as to whether those link types occur for the issue I was viewing. This will give me the ability to unselect link types I am not interested in. I would also like those settings to be saved for all issues I view. This will improve performance and provide consistency. The new behavior is confusing and inefficient.

I am hoping you can make some changes so I can roll out the html5 version of this plugin into production yet.

2 answers

This sounds like a bug. The intented behaviour was working just like in the Flash version. Therefore, it should remember all the filters and their status (checked/uncheked). The major difference is that the HTML5 version uses browser cookies and the Flash version uses SharedObjects (a sort of cookies supported by the Flash Player).

Maybe the cookie is corrupted. Might you try by un-selecting the autosave option (this should remove the cookie) and select it again (this should create a new cookie)? You might also want to try the 3.2.1 version. It enhances the way how the code is initialized becase I detected that some event listeners were initialized more than once. This might cause performance issues and maybe configuration corruption.

If the problem persists, please let me know and I will investigate it more.

Humm...

The add-on uses two cookies: one specific for the filters and the other for the rest of the user configuration. I've seen that the filters cookie is not always created... which is clearly is bug

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Oct 31, 2018 in Marketplace Apps

Marketplace Spotlight: Zephyr

Hello Atlassian Community! Each month, we run a series of Spotlights to highlight Marketplace vendors and apps that our team thinks this Community would find valuable. In last month's Spotlig...

313 views 0 1
Read article

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you