I have a Jira Service Desk and several Jira Software projects and when I am in a Service Desk ticket and I use the Create Linked Issue option/form, the fields are different than when I use the Create Issue form for the same project.
The Create Linked Issue contains only a handful of fields and the Create Issue form contains many fields.
I'm having a hard time finding what scheme/form I need to update to include additional fields in the Create Linked Issue form.
Hello @Lisa Tritt
Thank you for reaching out.
Indeed, it is not possible to change the fields displayed when creating linked issues. We understand how useful this functionality would be, so we created the following feature request:
Feel free to vote and watch the suggestion to increase its priority and also receive notifications about any updates.
For now, the workaround we have to enforce a field to be displayed in the Create Linked issue screen is to first add it to the create issue screen relevant to the project and
then, in the field configuration, configure the field as "Required".
Let us know if you have any questions.
Hello @Janene Pappas
You will need to apply those settings to all the projects/issue types you want to link issues. Basically, a required field enforces your link issue to open the complete create issue screen.
Giving you a practical example, let's suppose you have an issue in project A, and you want to create a new linked issue in project B. To ensure a specific field will be displayed when clicking to create a linked issue, you must:
Let us know if this information helps.
Hello @Denis Zvonov
Thank you for reaching out.
I just would like to say that the workaround steps provided are not the solution to any problem or limitation. They just provide a possible way to edit the linked issue screen, however, we are tracking the real fix for this limitation in the mentioned feature request.
That being said, the workaround provided was not meant to discourage or low the priority to address that limitation, but to simply provide you with a possible way to avoid that limitation, although it might not work for some use cases.
Let us know if you have any questions about that.
Actually your answer is the one and only thing Atlassian did regarding this issue. Better than nothing for sure, many other problems with JIRA don't have even a workaround. If you look at this ticket you will see that in almost 5 years - no progress.
And there are dozens or even hundreds of them. Obviously Atlassian has disinvested in the Server and DataCenter platform. Atlassian will regret.
Hello everyone, Hope everyone is safe! A few months ago we posted an article sharing all the new articles and documentation that we, the AMER Jira Service Management team created. As mentioned ...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events