How do I see custom issue types in a Next-Gen project backlog?

[Scott Wurman]

Hello, I migrated a batch of old "initiatives" that had been created in a Classic project a year or two ago over to a NextGen project that I just created. However, I'm now not seeing them in the new project and don't know how I can change the board to make them appear.

The initiatives were originally created to fit into a custom workflow built around ideas being evaluated and the approved, on hold, or rejected. I want to keep using that process but also wanted to archive all of the older ideas so we didn't lose them forever.

I used the Batch Move function from the Classic Project after creating a new Issue Type in my Next-Gen project that I also labeled Initiative, hoping that would allow me to map them to the same construct.

However, after moving them all out of the Classic Project and into the Next-Gen one with the Issue Type "Initiative," I can find them anywhere in the new project and can't see a way to modify the Board in order to have the custom Issue Types appear. 

[Angélica Luz · Accepted solution]

Hello Scott,

Thank you for reaching out to Atlassian Community!

Testing moving tickets from a classic project to a next-gen project, they are mapped correctly to the backlog. 

When bulk moving tickets, we must select the project, issue type, and status, so it was moved correctly to the backlog, so if the tickets are without a resolution, it should appear on the backlog.

Have you searched on Filters > Advanced issue search if the tickets show by filtering by project only?

Regards,
Angélica

[Scott Wurman]

Thanks Angélica. That was the solution I needed. It turns out that all of the stories came through marked as Done, which may have do to the custom workflow that was built for the Classic Project. Using the search you mentioned I was able to see all of them and then bulk update them to be in the To Do status, which means they now all appear in the backlog. Thanks again!

Scott