Post Functions not available in transition - even Jira admins don't see them

[Chris Chambers]

I'm trying to leverage a plug-in, called by a post function during an issue's transition. But when I go to that transition, Post Function, Validators, etc. are simply not visible.  Rules and Properties are there, but neither takes me to a Post Function.

I am a project admin, but our Jira admins have also looked and they don't have these options either.

Is there a setting within administration, for both, or either, admins and project admins that will allow post functions as an option?  Are post functions, validators, etc. a global function that needs to be enabled somewhere in admininstration?

Thank you

[Trudy Claspill · Accepted solution]

Hello @Chris Chambers 

Are you working on a Workflow for a Company Managed project or a Team Managed project? How did you navigate to the workflow editing screen?

In Team Managed projects there is no option to add Conditions, Validators, and Post Functions. There are a limited set of Rules that can be added instead.

For Workflows used in Company Managed projects Atlassian has recently introduced a new Workflow Editor.

https://support.atlassian.com/jira-cloud-administration/docs/what-is-the-new-workflow-editor/

If you have ended up in the new editor for a Company Managed Workflow you can get back to the old editor by clicking on the ... button in the upper right corner.

[Chris Chambers]

It is a Team Managed project.  So you can't do post functions, etc. unless you create a Company Managed project?

Might this also explain why, in a plug-in, I'm unable to see all of my Issue's fields, or even see them all under Custom Fields, even though they exist on the Issue Type?  Or for workflows, under Settings/[GearIcon]...Issues...Workflows none of my workflows appear?

Can a team-managed project be converted to a company-managed project?

Thank you!

[Trudy Claspill]

Hello @Chris Chambers 

The short answers are:

Yes

Maybe, Yes and Yes

and technically No.

Team Managed projects are intended to be stand alone, allow the Project Administrator to make customizations in them that will not be impactful to other projects. You can make your own custom fields that are used only in that project, and create workflow that are used only in those projects, and even create Issue Types that are used only in that project.

You will not see those custom fields, workflows or issue types in the Global configuration pages that are accessible through Settings > Issues.

Those Global configurations are to define elements that are and can be used in Company Managed projects. One exception is that Custom Fields defined with a Global Context can be reused in Team Managed projects.

Whether or not a given plugin is able to interact with Team Managed projects depends on the plugin itself. Some are constructed to work with Team Managed projects, and other are not.

Can a team-managed project be converted to a company-managed project?

You can't flip a switch on a project to change it from Team Managed to Company Managed or vice versa. You have to create a new project of the type you want, reconfigure it to match the source project as much as possible, and then Move the issues from the original project to the new project. Some information will not move successfully. For more details on that refer to this documentation:

https://support.atlassian.com/jira-software-cloud/docs/migrate-between-team-managed-and-company-managed-projects/

[Chris Chambers]

Thank you!  This has given me more/better direction than I've found in days of Googling.

[Trudy Claspill]

You're welcome!

You might find this documents useful also. They provide some comparison information of the two project types.

https://support.atlassian.com/jira-software-cloud/docs/learn-the-basics-of-team-managed-projects/

https://community.atlassian.com/t5/App-Central/Team-managed-and-company-managed-projects-in-Jira-Choosing-the/ba-p/2368866