Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Can I update a custom field in JIRA Portfolio? (except number and single line of text)


I'm using JIRA Portfolio on top of JIRA SW. I have defined a custom hierarchy - Feature - EPIC - Story. 

For issue type = Feature, I have setup a custom field in JIRA SW, say "My Status" which is a dropdown with value = In queue, Started, In progress, Complete, Deferred, On-hold.


During planning I want to create and edit Features in JIRA Portfolio, but not commit them to JIRA SW (so that development teams don't see this item). 


When I create this feature in JIRA Portfolio for the first time, I want to be able to update a value for this field "My Status". Is this possible? How?

(Note: I want to update this field during creation and not wait until commitment)

Currently, per my understanding any custom field (other than number or single line of text), cannot be edited in JIRA Portfolio and such custom fields are read-only. 



1 answer

Hi Siddhant,

Supposedly you should also be able to edit Single-select drop-down fields in Portfolio as well as the number and single line of text.  But I haven't been able to get it to work either.

This page specifies the three types of fields that should be editable:

I'm watching this issue, hoping for an answer.


I have same question.

I had forgotten about this issue.

Anyway, upgraded last week form 2.17 to 3.7 and this now works in both the live plans interface and the improved interface.  So, apparently, some time in the last year this was fixed.

The improved interface also makes it much clearer which fields are supported and which are not.

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events