Create issue to backlog

[Tim Arthur]

I thought I knew Jira well, but obviously not well enough. 

Use case: 1 sprint, 1 project backlog.

When creating an issue, the only status value available is Backlog.

The issue opens of course with status of backlog, but does not go to the project backlog.

Why? 

Second, if I remove backlog status from my sprint board, then the issue is invisible. Shows neither on the sprint (as expected) or on the project backlog.

Desired:

Create an issue, it lands in the project backlog. I thought each issue had to have a status assigned, so that'd be "backlog"?

Then, move issues from general backlog to sprint, and vice versa.

Thank you for your suggestions.

[Tim Arthur · Accepted solution]

Thank you Laurie and Nic. I created a dummy issue to inspect Jira's data flow and observed this prompt. I did not click Add to Active Work (Active Work is the name of our sprint). The other person's issue I was describing above, MUST have selected that option. A brand new issue defaults to status of BACKLOG as stated earlier. 

Next logical question then is how can I remove the "add to active work" as an option? If anyone has a quick comment that'd be great - else I'll open a separate request here.

[Nic Brough -Adaptavist-]

I don't believe you can remove that.

[Tim Arthur]

I opened an official support ticket so will reply here when I learn.

[Laurie Sciutti]

Hi @Tim Arthur ~ issues can only be assigned the initial status on create, in your case it seems that "Backlog" is your initial status value in your workflow.  If you're not seeing that in your actual backlog, check the column mappings in your Scrum board config ~ it may be that "Backlog" isn't mapped or that your board filter isn't actually including those issues.

[Nic Brough -Adaptavist-]

Hi Tim,

The backlog and the board are two views of the same thing - the list of issues that need doing (plus the board will show "done" ones from the current sprint) 

If you have not mapped a status on to a column, then as far as the board is concerned, the issue is not for viewing on the board.  As the backlog is another aspect of the board, the column mapping applies to it as well.  So yes, having your backlog status unmapped means the issue won't show on the backlog.

So, map the "backlog" status on to the first column on the board (actually, any column except the very last, but it rarely makes sense to have your backlog items in anything other than the "to do" column(s) on the left).

The second thing to look at is the board filter.  Could that be excluding the backlog status?