Post Function Not Working on Sub-Task Workflow for Assignee

[James Wilhite]

I'm trying to make it so that the assignee doesn't default to the project lead when a sub-task is created.  I read through several different discussions in this forum and decided that the best route would be to create a post function on a separate sub-task workflow to either copy the assignee from the parent, or to make the current user the assignee.  I've tried both of these post functions on the Create transition, and even tried adding in an earlier post-function that clears out the assignee.  However, no matter what I try, the assignee is set to the project lead.  

Can anyone help me figure out what's going wrong?

[Andre Borzzatto]

Thomas, first you would have to check your JIRA Global Permissions in order to check if the jira-users group is not the default group of your instance, which means that they are the only group who has JIRA Users Global Permissions, if they are, you can't, then, remove users from this group as they might lose access to JIRA as a whole:

• https://confluence.atlassian.com/display/JIRA/Managing+Global+Permissions

In a second point, about restricting projects for a set of users, you might want to review your Project Permissions and grant for each specific groups JIRA Browse Projects permission. This permission is the one that controls who has view permission over the project, groups assigned this permission in a permission scheme will be able to browse the project content.

This link contains a little more information about JIRA Project Permissions:

• https://confluence.atlassian.com/display/JIRA/Managing+Project+Permissions

I hope it helps!

[Juan Peraza]

Hmm?  I don't believe you can remove users from the jira-users group.  I believe membership in the jira-users is how JIRA licenses are assigned.  I think everything you did except removing users from the jira-users group is correct - you "added the project-based group to the roles for the project under Users".