Let's say I move an issue (OLD-10) and it beomes (NEW-20) in the new project. What happens to the OLD-10 link -- will it redirect? And if so, if I completely delete the OLD project, would a redirect still occur? Thanks.
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.
Perfect, thank you!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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#
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Can you please tell us about where these moved issue id are stored for jira Version 5.2.8 ?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks , i got my answer data is saved in Changeitem table
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.