We want to force the population of a "product code" field when a sub-task is created. For example if an issue is created with a product code of PC045 then we want any sub-task created to be populated by default (would be good if it could still be changed later) with PC045. This field is selected via a drop-down in the parent issue.
Yes, you can have fields inherit the value of the parents field.
In the create issue transition you can set the "Set Field Value from Parent" option in the post-functions. You can either do this in the default workflow you are using for the project, or make a separate workflow for sub-tasks. When only using this post-function, changing the value of the field in either the parent or sub-task will have no influence of the others value.
Hi Ben, I checked a test instance of OnDemand. The function becomes available after the 'JIRA Misc Workflow Extensions' have been enabled. As far as I could see, normal adminitrator privileges should allow you to enable this add-on through the "Manage Add-ons" section of your instance.
Hi Mick, I am unable to get this to work. I too am an OnDemand customer and have verified that the JIRA Misc Workflow Extensions add-on is enabled. I can get this post-function to work on any other transition, but for some reason it does not work on the Create Issue transition. Here are my post functions for the Create Issue transition: 1. Creates the issue originally. 2. Fire a Issue Created event that can be processed by the listeners. 3. The value(s) of field Due Date will be set from the issue's parent (replacing existing values). 4. The value(s) of field Environment will be set from the issue's parent (replacing existing values). Any ideas?
Aaron, I don't know if you have solved your problem yet - but try to put the post-function for Due Date on top. I had the same problem when I tried to set a datepicker and having it as the first post-function solved the problem. /Anton
Thanks for pointing out. As I am not quite familiar with JIRA OnDemand, I learnt that we can't install plugins on JIRA OnDemand. Sorry for not referrring the tags of the above question!. So can we expect change in the above policy for JIRA OnDemand in future?
I am trying to have the sub-task created with the same status as parent. I tried both of the below but the sub-task is still being created with 'New' status when I create one.
I tried to add the post-function 'Copy field value from parent issue (JMWE add-on)' [Set the value(s) of a field to the value of the same field in the parent issue] but this does not have Status field.
I have also tried to add a post function 'Copy Value From Other Field' to copy the status field from parent to sub-task which didn't work either.
How do I achieve this?
There's now a very easy to configure way to keep fields of parents and sub-tasks in sync using Automation for JIRA!
(this example transitions sub-tasks, but you could easily change this to edit the sub-tasks with a field value from the parent)
when i am creating a first subtask from parent issue it copies the values from one field to another but if i am creating second subtask from the same issue it copies the value of the same field from subtask not from parent issue from which i have created this second subtask.I am using post function Copy Value From Other Field.Please help
The Jira Software Cloud Team has been busy working on a simple, secure, and reliable way to integrate your build and deployment information from Jenkins with Jira Software Cloud. This means you don’t...
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