• 3
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Currently, Portfolio for Jira only supports the custom field types in this list:

      The following custom field types are supported:

      • checkbox
      • date picker
      • multiple-choice select
      • number
      • radio button
      • label
      • single-choice select
      • single-line text
      • URL (read-only)
      • user picker (single user)

      I would like Portfolio for Jira to support custom field types generated by third-party plugins.

            [JSWSERVER-25271] Support for third-party application's custom field types.

            Dear all,

            I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged.
            Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments.

            Sincerely,
            Aakrity Tibrewal
            Jira DC

            Aakrity Tibrewal added a comment - Dear all, I would like to inform you that this issue in the project JPOSERVER is being migrated to the new project JSWSERVER. Your votes and comments will remain unchanged. Our team at Atlassian will continue to monitor this issue for further updates, so please feel free to share your thoughts or feedback in the comments. Sincerely, Aakrity Tibrewal Jira DC

            Looking for support of "Project Specific Select List" field types as provided by the "Project Specific Select Field" JIRA Server add-on.

            David Mahoney added a comment - Looking for support of "Project Specific Select List" field types as provided by the "Project Specific Select Field" JIRA Server add-on.

            Developer of "Checklist for Jira" custom field here.

            The best would be to allow third party developers to implement their custom fields using a public API, but I get the feeling we're too late for that. Third party tools like "Structure" does allow any field to be shown in their lists because they took the decision to re-use the existing velocity template views that are used to render all fields on the issue in Jira Core. The same kind of limited design can be seen in Jira Service Management where the UI has been redeveloped and cannot be extended.

            If you allow the "Text (Read Only)" field type to be added in the Plan, your customers will be able to calculate this field with relevant data and add it to their Plan. Right now this can be done using a "Single Text" field but it will be editable.

            Maxime Lefebvre _Okapya_ added a comment - Developer of "Checklist for Jira" custom field here. The best would be to allow third party developers to implement their custom fields using a public API, but I get the feeling we're too late for that. Third party tools like "Structure" does allow any field to be shown in their lists because they took the decision to re-use the existing velocity template views that are used to render all fields on the issue in Jira Core. The same kind of limited design can be seen in Jira Service Management where the UI has been redeveloped and cannot be extended. If you allow the "Text (Read Only)" field type to be added in the Plan, your customers will be able to calculate this field with relevant data and add it to their Plan. Right now this can be done using a "Single Text" field but it will be editable.

            +1 we are using Tempo Accounts for tracking timelogs, would be great to use this custom field in AR

            Ye Fung Tchen added a comment - +1 we are using Tempo Accounts for tracking timelogs, would be great to use this custom field in AR

            I would like Jira Cloud - Advanced Roadmaps to support third party custom fields which are currently unsupported. 

            Javed Shaikh added a comment - I would like Jira Cloud - Advanced Roadmaps to support third party custom fields which are currently unsupported. 

              Unassigned Unassigned
              gperes@atlassian.com Gregory Peres (Inactive)
              Votes:
              36 Vote for this issue
              Watchers:
              36 Start watching this issue

                Created:
                Updated: