Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,298,441
Community Members
 
Community Events
165
Community Groups

When not to make a jira issue ticket and where to store the idea for future review

There are times you can get overwhelmed with too many tickets. 

when do you not make a jira ticket ?

and where do you store the idea for future review ?

2 answers

1 accepted

1 vote
Answer accepted
Brant Schroeder Community Leader Jun 24, 2022

@Great Ancheta That is a great question.  It really depends on your process.  I have been on projects / teams where we have created an issue / ticket for everything and ones where we did not.  On the ones we did not we used lots of different ways to log the information.  From my experience I like the teams were we created an issue / ticket for everything.  This was actually a much better way to be able to go back and review requests even if they were put on hold for years.  Here is what I would recommend.

  • Create a issue type in your project for these requests.  
  • Have a simple workflow that needs review, deferred, under consideration, won't do, will do.
  • Exclude this issue / request type from SLAs
  • Have a process where you review these requests regularly (Monthly or Quarterly)
  • Update filters and queues to exclude these requests so that they do not impact daily work
  • Have a process for closing out or moving these issues forward

@Brant Schroeder thx so much for this ! 

1 vote

Hi, @Great Ancheta !

I don`t have enough information about your needs, but I can suggest different ways and you`ll choose what is better meets your needs.

In SaaSJet`s team, we use backlog. So, you create tasks with ideas but don`t add sprint. So, there are no extra tasks in the active sprint, but you always have issues/ideas for the next period. 

  • Also, we use Forms&Checklists for Jira to store information inside Jira. We add Form to the issue and fill it with ideas whatever we need. or The example below

image.png

  • And one more suggestion, if you`re overwhelmed with too many tickets, transform it to the ToDo list with Recurring Checklists and Report. For instance, you need to check product releases or article publishing. You don`t have to create a lot of tasks to monitor everything. You will have only one but with Checklist. Add it to the task manually or automatically. In Jira issue, it looks like thatimage.pngPlease, tell me if any questions

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
STANDARD
TAGS
Community showcase
Published in Jira Service Management

Coming Soon: Insight Changing to Assets

The 2020 acquisition of Mindville added powerful asset and configuration management capabilities to Jira Service Management in the form of Insight. Following the completion of that integration, custo...

287 views 2 9
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