nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

"Set Field Value From Parent" Not Working with "Assignee"

rmacias12

I have placed a post function to set the Assignee from parent before the "Creates the issue originally" function, but after checking the created issue, I am seeing that it is still being set to the Project's default assignee (Project Lead).

Is there a special configuration I need to specify in order for this to happen?

Accepted answers

David _old account_

I have tried to reproduce your issue, to no avail. I set the Assignee from the parent issue just fine. Note that I put that post-function before Creates the issue originally.

Did you make sure that the parent assignee is valid for the subtask (authorization-wise)?

All comments

David _old account_

A couple of questions:

are you using the regular subtask feature, or pseudo-subtasks (based on links) managed by a 3rd party plugin?
did you try moving the function further down the list? Don't forget that JIRA will assign the issue to the default assignee during the issue creation. You must therefore make sure the function runs after that.

rmacias12

I am using a regular subtask feature.

Initially, I had set the Assignee Post Function at the very beginning, but I just moved after "Creates the issue originally" and it is still not assigning to the Parent issue's assignee.

Bharadwaj Jannu

Are you using JIRA Misc Workflow Extensions plugin, then check this plugin version supported with your jira.

I installed 2.5.4 in my standalone machine of jira 5.2.1 and it worked for me.

rmacias12

I am using JIRA v5.2.4 w/ the JIRA Misc Workflow Extension v3.1.1

The Transition's Post Functions go as such:

The value(s) of field Fix Version/s will be set from the issue's parent (unless the field already has a value).
Creates the issue originally.
The value(s) of field Assignee will be set from the issue's parent (replacing existing values).
Fire a Issue Created event that can be processed by the listeners

Only the Fix Version is getting the parent value, but the Assignee is not. I have even tried moving the Assignee to the beginning with no luck.

I would greatly appreciate any help as our organization would benefit greatly.

David _old account_

I have tried to reproduce your issue, to no avail. I set the Assignee from the parent issue just fine. Note that I put that post-function before Creates the issue originally.

Did you make sure that the parent assignee is valid for the subtask (authorization-wise)?

Bharadwaj Jannu

JIRA Misc Workflow Extension v3.1.1 worked for me with the same postfunctions (including order) added in my subtask workflow.

rmacias12

Nevermind its working. I think it is perhaps becuase I was using an issue that was generated before the plugin was installed? I just created a whole new parent task and now the subtaks are performing as expected.

rmacias12

Could clarify what you meant by "Did you make sure that the parent assignee is valid for the subtask?"

Currently I'm testing the feature with the Admin being the parent assignee, but then when I create the subtask, it just assign the issue the "Default Assignee" or "Project Lead" (which is me), the goal is to not have me as the assignee. Either way, all of the users that are in the parent issue have full permissions.

Anyhow thank you for your help I'll keep trying to see what the issue was. I would like to get this to work so I can convince my organization to purchase full license.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

addon-com.innovalog.jmwe.jira-misc-workflow-extensions