Hi all,
I'd like the option to assign a team to an epic upon epic creation. I have team included on the issue layout field for epics, yet, the option to assign a team doesn't show up during epic creation. Here's a look:
Thanks for the help!
-M
Hi Megan,
Thanks for the screenshot and it looks like you are using a Next-Gen project type, but currently Portfolio for Jira doesn’t support the next-gen project type and issue assignment to teams will not work on next-gen. You will need to use a classic project template to interface with portfolio at this time.
Some additional details on the functionality that is not compatible with next-gen projects and portfolio can be seen in the Documentation at "Portfolio for Jira next-gen support"
Regards,
Earl
Hi Earl,
Thanks for the note. This is actually in a classic project. Should I reach out to support? The goal is to be able to assign a team at epic creation.
-Megan
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Megan,
Thanks for the clarification, I got thrown off from the screenshot and I got the New issue view "Issue Layout" settings for mapping fields that you are looking at confused with the Next-Gen Issue type settings for the similar setting in the next-gen projects.
For the section you are looking at there is a limitation in the Portfolio Team field here on the create screen, and while the field can be surfaced in the Screen's of an issue it cannot be displayed in the Create screen because of how the mappings in portfolio work.
As portfolio is an add-on on top of jira if you are creating the Epic from Portfolio directly the field data is stored in a temporary location portfolio side until the data is committed back to Jira, however when setting the value in the Jira the screen directly, the screen is acting on the Base jira application side which does not directly access the portfolio functionality so it cannot store the data in the temporary location until the mapping is created post issue create and the plan can pick up the newly created issue. Because of this Portfolio Specific fields require the issue to exist for the field mapping to be created in the plan before the field can be altered from the Jira side.
So if you are using a Portfolio specific like the Team Field on the Create, Edit, & View screens it will only be avaliable on Edit & View screen after the issue is created.
We have the following Feature request to address this functionality, Please add a vote to help us track interest in implementation, also I added the link to the server version of the feature request as well incase anyone else finds this post looking for the answer:
Regards,
Earl
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.