HOW TO: Create Issue defaults to Backlog in Backlog, but Create Issue defaults to To Do in Kanban

[Luke]

Here's what I want to do:

1/ When in Backlog the Create Issue should add a new Issue by default into Backlog

2/ HOWEVER, when in Kanban, the Create Issue should add a new Issue by default into the Kanban under To Do

Currently, I can choose one or the other depending on Workflow config, but not both depending on location. 

Is there a way to change this? Since it seems odd to want to add Issue into Backlog when you're viewing Kanban (at least the way we work) and yet if I change the workflow, the inverse is true: now new Issues created in Backlog move into the Kanban!

[John Funk]

Hi Luke,

The question is how does Jira know if this is Kanban or not? If you are assuming because you create it from one board or another, it can't recognize this as a source. 

And I am assuming that the issues are created in the same project. Now, if there was a value for a field or some other way to know it is Kanban, you could have an automation rule auto-transition the issue to the To Do status. 

All of this is assuming a Company-managed project as well. 

[Luke]

Hi John, yes all correct assumptions. 

Created within same project(s) // Company-managed. 

Not sure there's a way for Jira to know if it's created on the Kanban if it's not 'built in' to the core code? 

But I do notice on some Teams Managed projects for example, that you can create an issue within e.g. a Kanban column. So I had thought there might be a way to do this for Backlog vs Kanban generally. 

It seems odd to have the Create Issue button NEXT TO the Backlog but send it into To Do, or, be in the Kanban view and have it set to backlog (maybe that's more acceptable). 

Maybe a good feature would be another Create Issue button in the Backlog but in the To Do section. But I digress. Presumably, this is a 'no solution'? 

[Luke]

Oh, and thank you for your feedback and time. 

[John Funk]

Well, basically the issue will go to the first status in your workflow for that issue type. So if you used different issue types with different workflows for the two, when they are created, they could go to different statuses. 

Or actually, the could use the same workflow and since they are using different issue types, you could create your automation rule to have a condition for the Kanban issue type and auto-transition it to the next status. 

[Luke]

Thanks @John Funk – probably something I'll just "live with" but what you say makes total sense. And it wouldn't make sense to be able to have multiple Create transitions in a workflow as there'd be no way to prioritise.