Issue in next-gen project appears in backlog but not in board

[Dillon Kenniston]

Hi. I'm using a next-gen Software project. I created an issue, and this new issue appears in my Backlog.

However, in order to get it to appear in my Board, I need to drag and drop the issue from Backlog view to Board view on the Backlog page.

Is there a way to automatically have the issue appear in my Board once the issue status matches a Board status column?

For example, if my board has a column for issues in "In Progress," and I flip the issue to "In Progress," my expectation would be that the issue automatically appears in my board column for "In Progress" issues, even if I don't drag and drop it out of my Backlog.

Thanks!

[Nic Brough -Adaptavist- · Accepted solution]

The move is simple - both ends of the link stay with it. Anything linked to OLD-10 will show NEW-20 on it as a link (it's not redirected though, the links are held as issue-id to issue-id so the view hasn't actually changed! Redirection only happens if someone goes to the old URL for OLD-10).

Deleting the OLD project will have no effect, you lose nothing.

Unless you create another new project called OLD, then when you hit OLD-10, your redirection will stop working. But your link between NEW-20 and other stuff will be fine.

[Paul Stahlke]

Perfect, thank you!

[Martin Cleaver]

Is that true programmatically as well? Say a script is writing time to OLD-10, will the worklogs actually end up on NEW-20?

[Nic Brough -Adaptavist-]

Mmm, it depends on your "programatically". Plugins will throw you an "unknown issue" in most cases. I'm not sure how REST handles, but I suspect it's the same - issue doesn't exist.

[Martin Cleaver]

Thanks Nic, yes, I meant via REST.

So, is there a way (over REST) to find the new issueKey for an old issueKey such that if an "add work log" call fails the application can pursue what where the time should be filed?

[Nic Brough -Adaptavist-]

Well, you can read the history of an issue via /jira/rest/api/2/issue/ISSUE-123?expand=changelog

But I don't know how to get there given only the old key.

[Martin Cleaver]

Thanks... so I've raised this as a new question at https://answers.atlassian.com/questions/319506/how-in-rest-to-find-the-new-issuekey-for-an-old-issuekey#

[Darryl Lee]

I have an add-on to this old answer - what if instead of creating a new project, OLD, you re-keyed NEW to OLD?

(Context: We have a project OLD created as a Business project, and they want to be converted to Software, which apparently requires a bulk move. Ideally they would be able to retain their OLD project key, but I think that this would break any old links, right?)

Thanks!

[sarang saini]

Hi Nic,

I need some help regarding this, As we move an issue from OLD to NEW and when we browse OLD it will redirect to NEW. I want to know from jira database schema point of view where this linking is stored. I go thru jira DB but unable to find where this redirect link is stored. please help.

Thanks

[BS]

in JIRA 6.4.x and above it's on the [moved_issue_key] table. 

[Ashutosh pandey]

Can you please tell us about where these moved issue id are stored for jira Version 5.2.8 ?

[Ashutosh pandey]

Thanks , i got my answer data is saved in Changeitem table