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.
You all at Jira did some weird stuff. If I select team managed project template then when I move items to done they get a checkmark and if I select company managed project template then when I move the items to done the issue ID is
crossed out. I'm curious did you hire two different companies/teams to code this? And they never compared the final output? I just need to know, so I can use it as an example of UI and teams not talking with each other. I like the checkmark and was hoping I could use it in the company managed template. Did your code paths really split that much?
Hi @Gregory Mester , im unsure if the Community can answer this fully, however I will provide my $0.02. As I understand it, Team Managed Projects was an evolutionary effort to create a next generation solution that was more simplified than the legacy CMP. It was intended to allow teams to manage their success with limited to no help from a Jira administrator. The code base is separate, I understand. I do not believe the goal has ever been to make the two the same on all UI fronts. My experience has been that TMP continues to grow toward CMP in capabilities and CMP gets some of the things that work well in TMP too. Personally, I like the
strike through for completed issue. You might wish to use the Feedback link in Jira to share your thoughts with the PM teams.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.