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 ?
@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.
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.
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...
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