Hello,
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.
Ideas?
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:
- As an administrator, I want to be able to change the create linked issue screen
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.
@Petter Gonçalves Can you please elaborate on
first add it to the create issue screen relevant to the project and then, in the field configuration, configure the field as "Required".
We are trying to do this and are not clear which project needs this adjustment?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you Petter, that does help.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You are welcome @Janene Pappas
Have a nice day and let us know if you face any other questions.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Just another perfect engineering solution from Atlassian. I am so tired of these things, they are just everywhere.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
https://jira.atlassian.com/browse/JSDSERVER-3917
And there are dozens or even hundreds of them. Obviously Atlassian has disinvested in the Server and DataCenter platform. Atlassian will regret.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Over two years after still no resolution... Why is Jira still advised by anyone as the go to solution for issue management still surprises me.
Sorry Atlassian, you had the lead, but you got greedy and you are now well behind your competition.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Petter Gonçalveshello!
Please tell me how can I understand which screen is used specifically to create linked issue?
If you specify a field as required, in my case it becomes required for creating a issue, although I only need to add it for the screen for creating a inked issue(
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi,
All good and well, but this work around only works for custom fields and not for system fields.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Is it possible to link and issue on the create screen while creating an issue with a issue on the same site?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.