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

any movement/plans for any additional supported custom field types?  nfeed fields in particular?

https://getsupport.atlassian.com/browse/PSSRV-60839
Request for the custom fields : project picker type" and "userpicker(multiple user)

Dear Atlassian Team, 

We are highly interested in such a feature to extend supported types of custom fields available for Jira Advanced Roadmaps. There are two cases:

1. We have developed many types of custom fields by ourselves for our Company's purposes. As of now they are "Unsupported". If we can make these fields "Supported", value of Advanced Roadmaps for us and our users will increase significantly. We are ready to re-develop our field types to make them fit your requirements to "Supported" types.
2. We have several plugins in use like "Component Picker", types of fields provided by this add-on are also not supported. 

Please implement this suggestion, as it will significantly improve user experience and value of the whole product.

+1 for also displaying of XRay test Management specific fields what is opften requested by our end users as XRay is the most used App in our 7000 user DataCenter instance. And so productivity could be increased for them if they also would be able to use Test Plan and Test Execution test run status fields within their Advanced Roadmap plans.

would like use Insight custom fields in Portfolio

+1 on mulit-line

+1 on nFeed

Our users are also heavily complaining why it is not possible to show multi line fields which they use in Jira. Especially a multi-line field "stakeholder summary" which we use.

+1 on the multi-line text fields. I have multiple users ask me often why there is no multi-line text fields available to edit or view in Advanced Roadmaps

Our biggest gap is not being able to use nFeed(Elements Connect) fields.  We pull a lot of information from a master source to keep teams organized and being unable to pull these fields in is a step back.

The addition of multi-line text fields is also a gap for us.  I have users asking me why that isn't yet available.  And read-only would be a good start.  I could sell that limitation simply by the fact that the multi-line text field was available for viewing.

Precisamos que o campo cascade (multicombo) seja incluído no Portfolio.

We are looking to add multi-line text fields to plans in Advanced Roadmaps. This will be helpful in presenting critical data to management. Also looking for an ability to make fields read-only to control data integrity.

In the case of Acceptance Criteria, we're using this at our highest level to set expectations for a multi-departmental Feature. It really does hamstring us that we can't add this field for view in Portfolio. We try to make our Summaries informative but at one point are they too long to make sense in the view provided? Whether it's right or wrong, our groups increasingly turn to Excel because it can offer high level view into complex items. Teams can easily add an AC column to a spreadsheet and are perplexed why this cannot be achieved in Portfolio. At the very least we should be able to add it to the "click in" view like the Description. But gold start would be to not have to.

Tenho a necessidade de criar uma issue direto do Portfolio, porem minhas issue tem campos customizados e obrigatórios.
Na versão 2.7 funciona perfeitamente, porem nessa nova versão 3.4 não funciona.

Without it Portfolio cannot use the whole potential. 

Any update on whether or not we add custom fields?  Not just add but EDIT.  Zero value if we have to go in ticket by ticket to update if it is view only.  Any and ALL custom fields should be editable.  What is the timeline to implement this? We are in need of it ASAP.  Seems no resolution to this?

I would like to be able to add a custom field type implemented as an Add-on, not just the standard ones developed by JIRA.  See Community Question here (https://community.atlassian.com/t5/Portfolio-for-Jira-questions/CustomFieldType-in-Portfolio/qaq-p/699309)

we too would appreciate if Portfolio would support all custom field types.

I would like to have the version picker custom field available in portfolio as well.

Is this feature request approved or targeted anywhere?

@cparra - you have to do it through the plan configuration menu - there should be a sidebar option for 'custom fields'... they're view only, but better than nothing... then you hit the cog in the scope view (top right of the backlog view (epic or story)) to select the custom field

I agree. I'm facing the same need for my product.

In the meantime, I cannot see how to add custom Jira fields to the Portfolio Scope view, can someone point me in the right direction? Thanks.

agree with people before me ... 

as JIRA Agile extends JIRA  functionality, JIRA Poltfolio should do the same.

It's not stand alone  application.  Separation only makes us frustrated by fact we can'y use JIRA our of the box elasticity and customization . All fields form JIRA should be reachable in JIRA Portfolio and all JIRA Portfolio fields exposed to JIRA.

Hi, I am also facing the same limitation. Need Labels custom field to be editable in Portfolio. 

@Alexey, completely agree. I am facing the same limitation.

Need single value listed box to be editable in Portfolio.

Custom fields are there in 2.1 but only text fields are editable. Fields with of complex types are read-only. It is surprising since the Fix Version standard field is multi-value. We at least need single-value list box to be editable.

This feature is so helpful! It will largely increase the usability for JIRA portfolio

Grouping issues/tasks are essential, and to use both JIRA and Portfolio seamlessly, those same groupings need to be available in both systems at the very least (if truly integrated). Having the data flow back and forth in both directions is ideal (and seems feasible given the "commit changes" framework is there). Right now having only components, labels and custom fields in JIRA yet only Themes in Portfolio is incomplete and seems like it will make it very challenging to utilize Portfolio for efficient planning (Full Disclosure: I and my team are new to JIRA/Portfolio and are in the planning stages of trying to configure JIRA/Portfolio for task management and program planning for our business).

Just a quick heads up: the BigPicture PPM plugin is capable of displaying any JIRA, custom or ScriptRunner field, along with grouping, sorting, searching etc inside these. It can be used alongside Portfolio to give you the desired overview.

Might like to be able to map Portfolio Themes to JIRA fields.

Components would be super helpful as that's what we use to identify different platforms within a project.

Can't wait until this one becomes available, this is really such a fundamental feature, I fail to understand why it is not available yet

Looking to use JIRA Portfolio for Scaled Agile Framework (SAFe). I'd like to have WSFJ displayed through Portfolio, but cannot right now.

This is a must have requirement for us too.

+1

+1 for this feature. I would like to add 'component' field. I also would like to use this tool for planning and tracking. As such I would like to add custom field for status tracking - for example: status indicator for feature (red, yellow, green)

Would definitely want to be able to add custom fields, in order to put detail on for project KPI etc.

This is a very big need for a current client of mine. They were immensely impressed with Portfolio but have some feedback.

Specifically we operate with multiple different small software types within one project, as multiple 'Components' are utilized within the single Software project. They would like to add an attribute to Portfolio so they can tag the Epics with the appropriate product/solution/software's that are targeted with the work.

Minimum, I need Components exposed. Ideally, I should be able to defined all custom fields.

This will impact our company financials: Our use-case is to be able to record the Sales Order number against an Epic within JPO; then to use that to link back to our ERP system so that changes to the End Date values in JPO will be reflected back automatically to the ERP system for overall business planning.

At present, it's a (very) manual process to try to keep the dates in sync between JPO and the ERP software.

This is a deal breaker for us. Fields such as Epic Proponent, ID<link to external site or confluence>, Multi value field such as strategic objective etc, are critical for this product to be a portfolio management software

actually at least the theme field is a must have for us

Being able to bring over custom fields, such as those used to define the benefits of a project, and see them when prioritizing/planning would be great.

Same problem here and "sync" like other field will be appreciated