You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
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:
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?
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.