Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
badges earned

Your Points Tracker
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

How can i prevent changing ticket description after ticket is scheduled for Sprint development?

Lot of times reporters/team members are changing ticket specifications after the ticket has been scheduled for a Sprint. 

We don't allow any requirement change after Sprint started.

Please help me if there is any way.


1 answer

1 accepted

4 votes
Answer accepted
G subramanyam Community Leader Apr 06, 2021

Hi @Sayeedul Islam Sumon welcome to the Atlassian Community.

When I read the team members/ reporters, I understand they have certain level of control on the Jira issues (as set in the schema by Admin).

1) One best way to restrict the modifications is to have a "working agreement" within the Scrum team members before Sprint starts.

You (as a PM/ SM/ PO), ensure team are adhering to the working agreement and except the designated role (in Jira as per your project permissions) no team member is liable to modify.

2) From the Jira ticket history, you will come to know who is frequently changing the ticket description. Talk to him and understand the root cause (requirements gap, understanding gap, breaking the user stories into task issues, communication gap within the Scrum team members) etc. etc.

3) You will get the solution if followed the above 2 steps.

Please stay safe and stay healthy.

Hi @Sayeedul Islam Sumon 

Agreeing and adding to what @G subramanyam suggests...

Consider having a conversation with the team to understand why/when/what the team would change in a description.  For example, perhaps the team adds clarifying details or assumptions discovered after work began.

If you want to improve visibility to changes, you could add an automation rule to make description changes visible after sprint start.  That would help in those conversations with the team, and provide ideas for your next retrospective about the issue.

Best regards,


Like # people like this

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Confluence

⚡️NEW Group for Confluence Cloud Admins

Calling all Confluence Cloud Admins!  We created a new Community Group to support your unique needs as Confluence admins. This is a group where you can ask questions, access resou...

97 views 2 8
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you