Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Default link value when creating new issue in related project from Service Management Project

Jochen Betz May 6, 2024

Working in a Service Management Project, the team members might need to seek support in specialist departments. In order to do so, they'll create linked issues. Each specialist department has there own Jira Project (normal, no service management). In addition there are other Jira Projects not affected by this at all and some other Service Management Project affected neither.

From this context it's clear, that the only meaningful relation type when creating the request to a specialist department is "is caused by". Unfortunately there plenty of options for the user to select something wrong. To avoid this I would like to

  1. either (and best) limit the possible values of this drop down list to "is caused by"
  2. or at least make it the default value
  3. -> In both cases, it should ONLY affect this particular service desk project, not any other.

How can this be achieved? The only similar question about this was this.

But in this case there are a) still all other values possible to be selected and b) it will affect ALL other projects.

1 answer

0 votes
Trudy Claspill
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
May 6, 2024

Hello @Jochen Betz 

With native Jira cloud functionality neither 1 nor 2 are available.

There is an open change request concerning customizing link types per project:

You might want to investigate third party apps that relate to issue links to see if any of those can provide the functionality you want:

Jochen Betz May 6, 2024

Thank you @Trudy Claspill for you fast and honest reply.

It's once more very sad to see how issues at Atlassian are treated. This one was created in 2009!?!?!?

I was aware of the fact that some functionality has been removed from Atlassian products just to bring them back as plugins you have to pay for or not at all or depend on 3rd party apps, even for things you would see as essential i.e for a buck-tracking tool.

This case/requirement might be different, but what it basically means is: Forget about this functionality. At the time it might be available (if ever) you probably will be retired.


Suggest an answer

Log in or Sign up to answer
Site Admin
AUG Leaders

Atlassian Community Events