Actually we are trying to Link Issues to the Parent. So we gave a Text field box and wanted them to update the Parent Issue Key and this will link to the parent when an Issue is created.
So customers are not updating is correctly, they are pasting the link, or not matching the key,
For Example: Updating only the numbers - 123 and not as JIRA-123
So facing some problems.
Could you please help us to find any ways for sorting this issues ?
Hi @Santhosh Raj ,
Unfortunately, there isn't a good native way to do this in Jira Cloud. The text field approach you're using is actually the typical workaround, and yes - those format errors are a common frustration.
@Sebastian Krzewiński mentioned My Requests Extension as one solution.
Another option is the new Cascading Issue Picker field (part of Awesome Custom Fields) - it was just launched specifically for this type of challenge. Instead of customers typing issue keys, they navigate through your issue hierarchy step-by-step to select the parent issue. No more format errors or wrong keys.
This eliminates the manual entry problem entirely since users click through structured options rather than guessing at issue key formats.
Full disclosure: I work for the company that makes Awesome Custom Fields, but wanted to share this since it directly addresses the issue linking problem you're facing.
By default I'm sure that search like you described is not possible. You need to consider use app like https://marketplace.atlassian.com/apps/1219647/my-requests-extension-for-jira-service-management?hosting=cloud&tab=overview
Regards,
Seba
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.