Content
View differences
Updated by Wieland Lindenthal 4 months ago
Customers and potential customers who used Jira before ask for this feature a lot.
From a UX perspective, it also is very helpful if you can see on first glance to which project a work package belongs. That is especially handy when they are used in environments where URLs are not expanded to preview cards like in Slack channels or e-mail applications.
In the first iteration we focus on allowing data migrations from Jira to OpenProject to keep the old Jira work item identifiers, ideally with all their historic former identifiers (for instance both identifiers, the one before and after moving from one project scope to another). We see a great value in allowing the Jira importer to be able to store the current Jira identifier as soon as possible.
In subsequent iterations we will make sure that those identifiers are used and are usable in most other parts of OpenProject where numeric identifiers are currently used, e.g. in PDF exports etc.
From a UX perspective, it also is very helpful if you can see on first glance to which project a work package belongs. That is especially handy when they are used in environments where URLs are not expanded to preview cards like in Slack channels or e-mail applications.
In the first iteration we focus on allowing data migrations from Jira to OpenProject to keep the old Jira work item identifiers, ideally with all their historic former identifiers (for instance both identifiers, the one before and after moving from one project scope to another). We see a great value in allowing the Jira importer to be able to store the current Jira identifier as soon as possible.
In subsequent iterations we will make sure that those identifiers are used and are usable in most other parts of OpenProject where numeric identifiers are currently used, e.g. in PDF exports etc.