For linking to other issues from within a Jira ticket, how do I change the default from "blocked by" to "related to"?
I've never once used "blocked by," but half the links I create end up being "blocked by" because I forget I have to choose "related to" — which is all the way at the bottom of that drop-down, and is "below the fold" 80% of the time, and I have to scroll the window before I can even see it.
99.5% of the time "related to" is what I need. How do I make it my personal default?
/fully anticipating one of the two usual Atlassian answers:
Hi, currently in Jira, when we click on "Link Issue", it shows a default link type. In your scenario, it is blocked because Jira displays this as a default value based on the order set in the settings. Jira sorts the issue link types alphabetically by their names.
Each link type has a Name, inward description, and outward description. In the issue view, we only see the inward and outward descriptions but not the name of the link type. So if you put "1" in front of the relates link type name, it will be prioritized as the first in order and set as default.
Thank you.
Good to know the logic. Thanks. But that's going to require a change made by an Admin, right? And that change that affects everyone, right?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, those changes need to be made by the administrator and they will affect everyone. However, the linking issues that we do are global. We can link issues from one project to another. I believe this is why they have kept it at a global level. I apologize, but currently there is no way to configure it only for a user or a project.
Thank you.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
It would be helpful to allow users to customize things like this. Different user and different teams have different areas of responsibility, and will use Linked Issues differently.
It wouldn't be so bad if the drop-down menu worked properly, but it doesn't. You can't scroll to the bottom of the drop-down unless you scroll the page so that the entire drop-down is visible. Users shouldn't have to perfectly align the page on their screen before being able to reach the lower items in the menu.
Atlassian makes really bad and unnecessarily convoluted UI/UX decisions. Another example is how it's impossible for users to choose their own date formats. It's ridiculous that every worker around the world has to use a date format on their own screens that was chosen by some admin halfway around the world.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I love this stated anticipation:
sad but true, and what keeps me from submitting bugs anymore.
however for sake of conversation here, it would be nice if one or both of these potential solutions were implemented:
1a) provide Sort Order arrows for us to arrange this list from that Action area of the UI (just like you can with the Resolutions list - heck, you can even set a DEFAULT with that list!) or
1b) at least give us an opsbar-sequence like property where someone (even if it's an Admin) can set the desired display order
2) give us the ability to manage this with Issue Linking Types and Issue Linking Schemes - I have a several projects in Jira that have much simpler requirements for Issue Linking choices.
definitely not going to bet on this ever becoming a priority :-0
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.