You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you move an issue from one Jira project to another, the system keeps an alias of the two ticket IDs, so either works for referencing the ticket. This seems to confuse ejira, in the sense that it thinks both the old and new ticket ID are different tickets.
For example, if I pull OLDPROJ-500 into my org files, then move OLDPROJ-500 to NEWPROJ, it becomes NEWPROJ-1, and both OLDPROJ-500 and NEWPROJ-1 end up pretty much identical between my two ejira ORG files.
Proposal:
Add a new psuedo state "Moved" for the old issue, so that it can be mapped to a distinct TODO task if desired.
Add a new property referencing the new issue ID.
The text was updated successfully, but these errors were encountered:
When you move an issue from one Jira project to another, the system keeps an alias of the two ticket IDs, so either works for referencing the ticket. This seems to confuse ejira, in the sense that it thinks both the old and new ticket ID are different tickets.
For example, if I pull
OLDPROJ-500
into my org files, then moveOLDPROJ-500
toNEWPROJ
, it becomesNEWPROJ-1
, and bothOLDPROJ-500
andNEWPROJ-1
end up pretty much identical between my two ejira ORG files.Proposal:
The text was updated successfully, but these errors were encountered: