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
Hello JIRA users around the World. I am starting the petition for Atlassian to roll back all recently introduced Team field related changes. Instead of making users' life easier, this so-called software "improvement" provided no benefits. Instead it presented a large number of PROBLEMS. I would love to ask people who came up with this "brilliant" idea why did they do it.
Finally, after heating another proverbial wall, caused by this "innovation", I decided to start this petition to force Atlassian management to roll back this monstrosity.
Please join me by adding your voice to this message. I have little hope for Atlassian to listen to our demands and act upon them. But maybe, if enough users will join together as one voice, Atlassian will do the right thing.
To Atlassian personnel on this forum - in my opinion, you have introduced useless and harmful "improvement" that has long lasting negative impact on JIRA Cloud system. Please roll it back.
Hello @Gregory Kremer
Speaking as just another user of the product, not a member of the Atlassian team...
1. Have you reached out to Atlassian Support to discuss the problems you are encountering?
2. What exactly are the "large number of problems" that you feel the change has introduced?
3. What is the scenario where you are "heating" (sic, I think you mean "hitting") a wall?
I have reached to them on several occasions now. Most of the answers were "It doesn't work".
Large number of issues would be a long story. We have several designed work-arounds that were supposed to fix shortcoming of the original (Advanced Road Map) Team field, as it was (and still is) locked. When merger of the Team field occurred, we started to get duplicate team names, because everyone could create a Team in the collaboration tool (Team tab). That completely screwed up our work-arounds. I still can't comprehend why creating a team could be done by anyone now, while only admins could create Team in the ARM before, giving them some control over what is happening.
And the last straw was when we discovered that after this "improvement" the Team field was not longer available in the Two Dimensional Filter Statistics gadget, which we widely use, as Team is one of our main fields for metrics reporting. And the answer was buy a $4000 add-on, or there is some complicated work-around that requires programming/development.
All and all, we saw absolutely no benefit from this change - the field was Locked and remained locked afterwards, which means we still have to use team IDs, while querying, instead of the actual team name. Even worse, before team IDs looked like 10, 20, 30, etc. and could be memorized by people who used queries often. Now it is something like this- 318e85d5-ccbb-4dcf-b2c8-54fdf839c39a. Memorize that please.
There is already a bunch of internally crated "improvement" issues, related to this implementation.
It wasn't a well thought out "improvement" to begin with, but then they forced it on all of us, without the option to bypass it if we wanted to.
I might be wrong (I honestly don't think I am), but can you name me a single positive/benefit of this change? I've spoken with some of my counterparts in other organizations, and all of them were of the same opinion as mine.