nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

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

Great Ancheta

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 ?

Accepted answers

Brant Schroeder

@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

All comments

Karyna Tyrnavska _SaaSJet

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 Smart Jira Forms to store information inside Jira. We add Form to the issue and fill it with ideas whatever we need. or The example below

And one more suggestion, if you`re overwhelmed with too many tickets, transform it to the ToDo list with Smart Jira Forms. 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 thatPlease, tell me if any questions

Brant Schroeder

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

Great Ancheta

@Brant Schroeder thx so much for this !

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

cloud

jira-service-management-cloud

jira-service-management