Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

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

Editing a custom single-select field opens a full edit popup screen (Jira Server)

I have a custom field with 5 options. When I create an issue, I get a drop-down with None and the other 5 options. So far, so good.

However, when I view an existing issue and go to that field, I get the pencil icon and it says, Edit popup form enabled. And when I click on the pencil, I get a popup with the full issue.

Until very recently, this field worked as expected - the pencil icon said, Click to edit.

One of the references below mentioned the Move Issue permission, that I may have added, but my Jira user always had it since I'm the project admin, so it does not make sense.

I have no idea why I get this behavior on some fields and the desired behavior on others. There is nothing in field configuration that mentions these two behaviors.

Since I have not changed any field, I wonder whether this is a global Jira behavior that may have been changed by the Jira admin team.

Here are two references, but none provide a satisfactory answer/resolution:

https://community.atlassian.com/t5/Answers-Developer-Questions/How-to-disable-pop-up-option-for-editing-an-existing-issue-in/qaq-p/463210

https://community.atlassian.com/t5/Jira-questions/JIRA-5-1-2-questions-re-pop-up-issue-edit-window/qaq-p/261017

This is for Jira server, version 7.11.

3 answers

1 accepted

1 vote
Answer accepted

Well, sometimes one needs to RTFM!

In the ScriptRunner documentation, under the Limitations section (link below), they clearly state:

On the View Issue screen, trying to edit a field with a behaviour will launch the edit issue screen, instead of the normal inline editor.

Limitations

We plan to submit a change request as this seems to be the designed behavior...

1 vote
Rachel Wright Community Leader Dec 04, 2018

Hi @Amir Katz, I don't know but I'm interested in the solution!  I only see the "Click to edit" option when I tried this in my Server 7.12.1 instance.  Can you post a screenshot of what you're seeing?

Next, can you make sure your custom select field is present on the "Edit" screen (not just the "Create" screen?)  In the past, I've tried to edit something inline and realized I couldn't do it because the field was missing from the correct screen.

Finally, are you using any add-ons that could be changing the behavior of the field?

Sorry I don't have the answer, but maybe with some additional info, someone from the Community will know!

Thanks,

Rachel Wright
Author, Jira Strategy Admin Workbook

Rachel,

To your questions:

1. All these fields are present in the Edit screens.

2. When I hover over a selection field, a pencil icon appears.

    If the field does not have a Behaviour, the tooltip says Click to Edit.

    If the field has a Behaviour, the tooltip says Edit popup form enabled.

3. The only relevant add-on is ScriptRunner. There are many other add-ons in our system, but AFAIK, only ScriptRunner modifies the JavaScript behavior of field.

TG-2.pngTG-3.png

Like # people like this

Hi Amir, were you ever able to solve this? We're seeing the same behavior on the Description field in a particular project, and I'd really like to have it as a normal inline edit.

I have not touched this since posting my response (to my own question). It was just an annoyance, not really a bug.

In any case, please be aware that Jira is migrating to the cloud, and Behaviours will not be supported there, so don't pin your hopes on them.

Amir

Suggest an answer

Log in or Sign up to answer
TAGS

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