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
Next: Root
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.
For the Love of G*d - is it a company permission issue or is it just difficult to delete old stories/issues? We have open stories from 2015 - that we are no longer working on and the reject button produces an error (looks like a bug) and the delete button doesnt exist. Anyone else having this issue?
Thank you- I was told the reject issue is a bug and that it has been reported through JIRA support.
So for right now- what we have done is our SCRUM master created a "Can be deleted Sprint" So I can move stories into that sprint and then "someone" will have to go in there - that has the delete permission- and delete them.
With my knowledge= they said I could reject- because the data stays there but they dont want me deleting. Thus the work around.
It's horrid when you are forced to work around things your admins should have fixed! The tool is supposed to be there to help you, not get right in the way.
(I'm mostly blaming the admins - there's aalways a chance of a Jira bug of course, but the symptoms you've got scream "broken transition, caused by bad config or a broken plugin." Either way, your admins should have fixed it)
I understand- now we have a sprint called "delete these' and I bet- a year later- it will still be there because people hate deleting anything.
Assign them all to the admins and keep re-opening them until they fix the problem ;-)
I know, very passive-aggressive, but your admins are failing you and need to do better.