Details
-
Suggestion
-
Resolution: Duplicate
-
None
Description
NOTE: This suggestion is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding suggestion.
Hi everyone,
Thanks for voting and commenting! This issue is being addressed as part of the all new Portfolio live plans, which feature an entirely overhauled and more seamless integration model with JIRA Software / Agile. Live plans are currently available as a labs feature for both Server* and Cloud, so you can start evaluating them without any risk of impacting existing Portfolio plans. They are not yet feature-complete, we're working on bringing all major capabilities of standard plans back into live plans on top of the new integration model before we graduate live plans out of labs and make them the new standard way of working.
Please check out this blog for a summary and short videos of how the top-voted suggestions are being addressed with live plans: Top 10 suggestions addressed in live plans and join our Portfolio Pioneers LinkedIn group to discuss feedback and best practices!
Thanks,
Martin Suntinger
msuntinger@atlassian.com
Principal Product Manager, Portfolio for JIRA
*The live plans labs feature is available with Portfolio for JIRA 1.12 or higher. It is compatible with JIRA Software 7.0.5 or higher, and JIRA 6.3 or higher, in association with JIRA Agile 6.7.12 or higher.
When I import issues in Jira Portfolio, I would like to import assignees that already exist on Jira tasks and user stories.
Some fields are already filled when we "Import issues" : Parent epics and releases. It would be great to also have the assignee filled because very often, when we create tasks in Jira, we already know who will have to work on each task (but we don't know when). And the problem is that when you import dozens of tasks in Portfolio, that were already assigned in Jira, you have to reassign (to force the assignment) all these tasks manually in Portfolio (and so you have to make the assignment job twice).
So, the "import issues" panel could allow to have more columns such as "Assignee" and why not "Sprint" (because sometimes, when importing a task in Portfolio, we already know in which sprint we want to affect this task).
Thank you.
Attachments
Issue Links
- duplicates
-
JPOSERVER-161 import assignee
- Closed
-
JPOSERVER-477 Allow for importing of assignee when importing issues from JIRA to Portfolio
- Closed
- has a regression in
-
JPOSERVER-1406 [Portfolio Live] Teams and Members don't seem to always get read from the JIRA issue assigne
- Closed
- is duplicated by
-
JPOSERVER-161 import assignee
- Closed
- relates to
-
JSWCLOUD-20091 Allow to import assignee when importing issues
- Closed
- mentioned in
-
Page Loading...