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

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,458,126
Community Members
 
Community Events
176
Community Groups

Is there a way to create a new child issue automatically linked to its parent in the issue view?

Similar to how sub-tasks can be created in the issue view and linked to their parent task (see image #1 attached), we want to be able to create a new child issue and have it automatically link to the parent task (by pre-filling the "Parent Link" field in the Create Issue window). Is this possible? We have ScriptRunner, so we're open to the idea of utilizing that to do it.

For context, the problem we're trying to solve is that our users aren't filling out the "Parent Link" field for various reasons (mostly just forgetfulness), so we end up with a high number of orphaned issues. We want to make issue creation in the hierarchy as streamlined as possible.

Current versions of what we're using:  Jira Server (7.13.0), ScriptRunner (5.6.1), and Portfolio for Jira (3.9.0).

Task-Subtask.PNG

 

MasterTask-Task.PNG

1 answer

1 accepted

0 votes
Answer accepted

Hello Kelly,

Unfortunately it is not possible at this time.   Portfolio Fields have some some limitations in the current design. Primarily they are  not a fully recognized fields in Jira but managed in the portfolio application directly and details are passed from portfolio to Jira about the field contents.  There is not a direct call from the api to the field but rather a managed field by the application.

Additional details on this can be seen in the following Feature request where we are tracking interest in updating the behavior to allow for additional integration such as ScriptRunner or adding in native options such as making the field required on the create screen, make sure to add your vote, and add yourself as a watcher if you want updates on the request:

But overall the parent link field (and the other portfolio specific fields As covered here) are based of the calculations run in the portfolio application and stored in a different location than custom field values.  For a detailed look at the mappings, If you look in the database tables and see the mappings int the json_value  column of the property_entity table with the query:

select * from entity_property where property_key = 'jpo-issue-properties';

Because of the portfolio application handling the values add-ons like ScriptRunner are not able to pull a direct field value, and there is a discussion about this in more detail with some feedback from Adaptivist Support about the functions in the following post:

Regards,
Earl

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events