How to find issues that reside only in Next-Gen projects?

Valentin R.

Hey! Is there a way to JQL only the issues that live in Next-Gen projects? I need to separate those from "Classic" ones and use it as a condition for automation.

Maybe there is something specific in Nex-Gen issues that classic issues won't have?

Thanks.

Bill Sheboy

Hi @Valentin R. 

Your question seems like a good idea for some circumstances, and...

After checking a bit, I did not find anything obvious to query for this distinction.  There are fields which should be unique to each type (e.g. Story Points vs Story Point Estimate), but there are no restrictions preventing the mis-use in the other type.  I just found some Classic projects in my instance with Story Point Estimate set.  :^)

Checking the REST API, there is an attribute of "style" (classic or next-gen) but it is not accessible unless you called the REST API from the automation rule for the issue's project.  That seems a bit heavy-handed.

And, I didn't see anything in the suggestion backlog to make this information available.

If these are project-level automation rules, I recommend creating different versions based on the containing project.

If instead these are global/multiple-project automation rules, you may want to either:

• create a list of projects to check in a condition in the rule
• add a custom field to indicate the difference, and set it bulk-update to start and automation later

Best regards,

Bill