Team Managed JSM / Next Gen projects & Approvals

David Quiram

I think I know the answer here, but want to make sure this isn't just a bug or a misunderstanding. 

I am looking at these new Team Managed JSM projects I got an email about and trying to see what their limitations are. Specifically I am looking at the approval workflow feature or lack thereof.

Where my confusion stems from are articles like this:

• add-an-approval-to-a-request-type-in-team-managed-projects 
  • This article clearly states in the title that these directions are for Team Managed Service Projects and approvals are present
• what-are-the-different-workflow-rule-types 
  • This article looks to be intended for these new project types and doesn't indicate approvals as an option at all

This feels like a situation where "Next Gen" projects are not quite as feature rich and the documentation is not making a clear delineation between things. It's like Next Gen projects are team managed projects, but not all team managed projects are Next Gen projects. 

Similarly, Jira Fields are available in team managed projects, but not Next Gen projects as there is misleading documentation around this as well.

Am I the crazy one here or are different effort groups in Atlassian not using the same verbiage? 

Mikael Sandberg

NextGen isn't a term anymore in Jira, that changed to team-managed project (TMP).

The KB you found about rules are for the new workflow editor that is coming out, you no longer have conditions, validators, post functions etc in it that you currently have in the old one. And if your project is a TMP JSM project you do have the approval process.