You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
When we create a sub-task, is there a way to populate some of the fields before hand so that user does not have to type them again?
I used an automation rule to accomplish this.
The rule is run when issue is created (I also made a second rule to be used when issue is updated to continually refresh the subtasks).
Use a branch rule and specify sub-tasks.
Use the "Edit issue fields". Select all of the fields you want to populate. Select where you want the information to come from (trigger issue, parent issue, epic issue).
It worked for me!
I also didn't want any users to edit this information. So I created a copy of my screen and named it "read-only" and then I removed the fields from this screen. In my screen scheme, under the edit operation, I associated the read-only screen. In my view screen, I have all of the fields. So now the user can view all of the fields but not change.
Hi @[deleted] ,
i have never done it before but my first thought is to create a custom script listener (maybe) with Scriptrunner addon so it can take values from parent issue and copy them to subtask.
Go to the workflow of this issue. Find the create transition and in there, exist a post function tab. Click to add a post function and check the option "copy field values from parent to subtask issue".
One Query, Post function will be executed once the user saves the sub-task, right? Or it will be before that.
FYI we want to pre-populate the values when use clicks create sub-task from the parent Story/Task and the form gets loaded.
Hello @[deleted] ,
What do you mean after the user saves the subtask?
Another thing that u should do! Create a test environment of the instance... Make any changes and tests that you want and if they are working, apply them to the production instance
What I mean is when user clicks on new sub-task, does the post-function apply before the user sees the sub-task form or post-function applies when user clicks Create button after entering all the details on the sub-task form.
Also, can the post function be executed based on issue type(sub-task) in this case?
We are using JIRA cloud. is it possible to create test instance there or should I work with a test project?