next-gen issue creation only in backlog

[Delta Development]

Hi all,

We try to block the creating of tickets directly in the next-gen board by users (+Create Issue). We would like to force them to create issues in backlog only (our issue pool).

The assignment of tickets and the 'move to board' action should be done by team-/projectleaders only.

Can't find out how to organize this in Jira.

Best regards,

[John Funk]

Hi @tjarcoboerkoel   - Welcome to the Atlassian Community!

There is very little customization that can be done with Next-gen projects/boards. Particularly, you cannot limit actions by one person versus another as you would like to do in your example. 

[Delta Development]

Hi @John Funk ,

Thank you for your answer.

As teamleader I need to have the control of issue movements from backlog to board in next-gen Jira. I need to check issues for completeness and assign to a team-member before moving to the board.

Also, when a ticket is created it should always be defaulted into the backlog (where it is for).

I don't quite understand why this not the default location for issue creation in first place, because issues created on the board can't be moved to backlog. I think the current workflow is not logical.

Could you create a request for this?

Best regards,

[John Funk]

When you create an issue on the Next-Gen project, what status is it going to? 

[Delta Development]

It goes into the backlog, i don't give it a status so now it just defaults to the first card of the kanban board (assigned in our case). I can live with that.

When I move it to the board it gets "assigned" and the "assignee" will get a notification of the new task through automation.

Created issue in the backlog could also be "unassigned" or empty (and filled in when moved from backlog to the board with name of First kanban card), would all be oke I think.

[Delta Development]

@John Funk 

As addition on above, we managed to get this in the workflow forcing "on create" of issue with "transaction the issue to" backlog, but the issues created directly in the next-gen board (for example "ToDo") are not moved to backlog.

There seems to be a flaw in the automation.

Transition issue

Destination status could not be resolved. If using a smart-value ensure this resolves to a numeric status ID or untranslated name for issues (with current status):TCKTS-14 (ToDo - 10056)

I've added a screenshot of the rule: