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 do you identify or search for incoming issues in a next-gen project?

Is there a way to identify newly-created issues (either those created by other people, or those created by our own team members) in a next-gen project? There doesn't seem to be an incoming state like "Triage" that I can use to accomplish this.

What do others do to handle this?

2 answers

0 votes

Hello mrwiggles,

Thank you for reaching out to Atlassian Community!

Checking your subscription, I see that on your site there are Jira Software and Service Desk and both of the products have the option to use next-gen projects.

As you didn’t mention what product is, I’ll post here the best way to check for both.

If it’s related to Service Desk, the best option is to use the queue where you can customize the order of the issues and it’s easier to see new tickets.

If it’s a Software project, you can create a filter. It’s basically a queue, but in this case, you can’t access it directly from the project. From the main page, click on Filters > Search issues.

On this page, you can edit the columns for it to show the information that you need and filter by the project, order, status and so on.

Hope this helps!


Hi Angélica - thank you for the detailed answer. I'm using JIRA Software. For some reason it didn't click that I could use JQL to search a next-gen software project via the search icon at the side: I'd read that next-gen software project could not have custom searches so I didn't even think of it.

Second - what are the recommendations for identifying new tickets created for a next-gen project? I have a project with tickets that will be created by multiple people, and it's pretty hard to figure out which ones are incoming and those that I've looked through, given that there's only a "TODO" status.

I tried to work around this by creating a new dropdown called "Triage Status" and setting a default value of "Incoming". When I create new issues however, I notice that this field has no value.

You can create more status on a next-gen board. 

The first column is ToDo and the last one is Done and all other statuses between those two are In Progress. So if you create a status called Triage, it will be ToDo and the next status will be In Progress, so I'm not sure if it will work for your use case.

When searching for an issue, you can filter by created date and the first of the list is always the one. Your workaround is a good option, but the user will have to let the default status when they create the ticket.

I tested here and added two values and when creating a ticket the field already shows "Incoming" and when created, the value is correct.

Screen Recording 2020-01-20 at 03.40 PM.gif

So, to check all new tickets you can filter by project = "project name" AND "Triage status" = Incoming

Hi Angelica - thanks for looking into this. I opted _not_ to go with creating more columns, and instead went with the field. I'm not seeing the behavior you are, however. Even after setting a default for a new field. Using the "+" button at the side gives "None" as the default.

Hi @mrwiggles

Would you mind to send us a screenshot of the custom fields?

I just created a dropdown field with two values and added one as the default.

Screenshot 2020-01-28_09-42-10-683.png

@Angélica LuzI figured out the situations where this happens:

  1. You move a ticket from an existing project to a new-style project. Despite "Incoming" being set as the default, the "Move" workflow allows the user to select "None".
  2. You create an issue via the Roadmap page.

Thank you for the details @mrwiggles

I was able to replicate the issue while moving a ticket. Based on that, I created a bug:

Please, click on "This affects my team" and also watch the bug to receive updates.

Regarding the Roadmap, creating a new ticket shows the default value correctly. Just to make sure we are on the same page, you are talking about the Roadmap directly in the project and not using an add-on like Portfolio, is that correct?

Suggest an answer

Log in or Sign up to answer
Community showcase
Published in Team-managed projects

4 steps to get actual statuses on the Jira board.

Jira   is a powerful tool   that helps teams to plan, manage, and report on their work.   We love using Jira, especially for its ability to track issue progress. But how to monitor the...

1,152 views 10 14
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