Showing Portfolio custom fields in Jira



アトラシアン コミュニティをご利用ください。


You can make certain Portfolio for Jira custom fields display in your Jira issues. This is very handy in providing two-way communication between both Portfolio for Jira and Jira. 

The following custom fields in Portfolio for Jira can be configured to display in Jira:

Parent link

You can define arbitrary parent-child relationships between issues, and then show the parent link field in both Portfolio for Jira and Jira.

In a Jira issue, you can see and edit the 'parent link' field in your Jira issues.

You can also see the child issues of the parent.


Conditions to consider...
  • You can't set a parent issue of an issue that is already at the top of the hierarchy in a Portfolio for Jira plan.
  • You can't set a parent link for an issue for the following cases:
    • if the epic link for the issue is already set, or
    • if the issue is a sub-task of an issue.
  • Epics don't show up in the parent link — you must use the epic link instead.
  • The parent that you set has to match the hierarchy configuration. For example, when using the default hierarchy levels in Portfolio for Jira, you can't set the parent of a story to be an initiative. In this case, the parent would be an epic, not an initiative.
  • Jira can and will let you convert a story with an epic link into an initiative, if need be. However, a warning will be displayed for that issue in Portfolio for Jira – indicating that the issue doesn't coincide with the hierarchy configuration in Portfolio for Jira.

When you assign a team to an issue in Portfolio for Jira, the team is reflected in the Jira issue as well. You can also change the assigned team in Jira, and that change is reflected in Portfolio for Jira.

Team in the People section of a Jira issue


Conditions to consider...
  • To see the team field in a Jira issue, you must assign a team to the issue in Portfolio for Jira. Find out more about teams here.
  • If you assign a plan-specific team to an issue, you will be able to see it in the issue. However, unless you make the team a shared team, you won't be able to assign a plan-specific team from the issue itself.
Target start and target end dates

Target start and target end dates are directly communicated to your team via Portfolio for Jira plans. The team, however, may be updating dates of their own on Jira issues, since they work directly on these issues in Jira.

By having these fields display in both Jira and Portfolio for Jira, target start and end dates will then display in Jira issues.

Target start and target end dates in the scope table of a plan in Portfolio for Jira

Target start and target end dates in the dates section of a Jira issue

Displaying custom fields in Jira issues

  1. Go to your Jira application >  > Issues.
  2. Click Custom fields, and then find the custom field you want to display in your Jira issues.
  3. Select  for the custom field > Screens.
  4. Select the screens you want to add the custom field to, and click Update.
  5. To add target start and target end dates, perform the following steps:
    1. Go to your Jira application >  > Issues.
    2. Click Screens, and then find the screens that you're using in your Jira project.
    3. For each of the screens, click Configure. This will display the fields in the order that these fields are being used in the selected screen.
    4. Enter Target start for the field name, and then click Add.
    5. Enter Target end for the field name, and then click Add.
    6. If necessary, drag and drop the target start and target end fields in the order that you want these to appear in the selected screen.
最終更新日 2017 年 11 月 27 日


Powered by Confluence and Scroll Viewport.