Can I get just-created stories into a new sprint board column?

[Phil Bustin]

In the Sandbox, I was given a requirement to automatically place Development issues into a sprint board new first column.

In board Settings, I moved the unique (not shared) first status for issue type/workflow "Dev Story" issues to the new first column. 

However, I need do the same for old workflow "Story" issues, whose first status is To Do, shared with other workflows and currently appearing in the second (To Do) column.  In fact, for a while in Production, only the "Story" issues with the shared first status will be created, because it will be a while before I can build the new workflow in Production.

I'd like to find a solution for automatically moving "Story" issues, with shared first status "To Do", to the first sprint board column.  I suppose I could simply replace the "To Do" column, but that is needed for non-Development issues.

I guess the obvious solution is to create another interim Dev Story workflow for Production, until the Sandbox Dev Story workflow is painfully created from scratch in Production.  The interim workflow would differ only from the Story workflow in that the first status would be unique (perhaps "Dev To Do").

[Prakhar Srivastav {Appfire} · Accepted solution]

@Steven Sproat

If you provide issue key as field while importing the csv then it will update the existing issue and you will not need to delete them.

 Check Update existing issues in the below documentation link :

https://confluence.atlassian.com/adminjiracloud/importing-data-from-csv-776636762.html

Regards

Prakhar

[Steven Sproat]

Hi,

Thanks for the reply.

I've ran it through but keep hitting this error,

282 of 282 issues have been skipped because they already exist in destination projects.

Could this be because  JIRA has changed all my issue keys from what's provided in the CSV? I had a mixture of keys in the CSV and it looks like JIRA has consolidated them all into my new project key

[Prakhar Srivastav {Appfire}]

@Steven Sproat

You should provide the issue key that are present in your jira system (where you are going to import ) right now. 

That is the way for jira to find your issue and update it.

Regards

Prakhar

[Steven Sproat]

ah I was concered that'd be the case, that means having to go and cross-reference nearly 300 keys back and forth....I'll not bother and just live with it.

Thanks for your assistance.