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

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

why "Select List (single choice)" custom_field in JSD version 4.13.0 portal is read only ?

We upgrade JSD to 4.13.0 and we are using Jira core 8.13.0

the custom field is read-only in the portal and we can not drop down the list.

The agent can update the field in the issue after creation.

I try with a user with admin privileges but I got the same problem.

does anyone faced such a problem should we downgrade to another version?

 

 

1 answer

1 accepted

0 votes
Answer accepted

There can be multiple reasons, but you may want to star from checking field's placement on screens, make sure that it is the part of Create screen. Then check fields settings for the specific request type and make sure that it is present in fields.

If both is correct (fields is present on Create screen and in request type), you may want to check automations and other customizations which is much broader topic.

But I do not have a problem with the field when I use Create to create a new issue or with 'Edit'.

The custom field is not editable in the PORTAL side.

the problem appeared after upgrading 

I am sure now that the problem came after upgrading and nothing else because we got the same after we run upgrade on a test server. 

Do you have ScriptRunner installed with version 6.12.0? If yes, use 6.11.0 instead. The 6.12.0 version seems conflicting with Customer Portal functionality for whatever reason. We encountered the same issues and ScriptRunner 6.12.0 was the culprit. 

Like Juhaina Almama likes this

I am changing to 6.11.0 and this solved the problem  

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira Service Management

Why upgrade to Jira Service Management Premium?

We often have questions from folks using Jira Service Management about the benefits to using Premium. Check out this video to learn how you can unlock even more value in our Premium plan.  &nb...

203 views 1 6
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you