Community moderators have prevented the ability to post new answers.
You can place it only in your view screens (remove from edit screens). Users will probably need to enter a value to it in a certain stage (creation, transition) - that's your option to add it for edit.
Thanks for your answer.....but how to remove it from the edit screen...
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
The easiest way to navigate to this is to go to the project, look at the settings, find "issue type screen schemes" and click on that. That will tell you which "screen scheme" is in use for each issue type (often, it's only one), so select the one you are interested in changing and go into that. The screen scheme now tells you "I am using screen X for create, Y for edit and Z for view". Again, there may only be one or two screens there. You will need to split it up if X, Y and Z are all the same screen - copy that screen and rename it to something clear (I usually add "for edit" or "for create and edit", so it's clear what it is for), then amend the screen scheme to use the new screen for edit. Finally, once you know what screen is in use for edit (and it's different to View and Create), go into the screen and delete the field from it
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I followed your steps, but my field is not added to Edit Issue Operation it is only added to View Issue, still it is editable. What should i do now?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You've still got it on edit, you probably looked at the wrong screen (the screen schemes are quite complex to work through, because they're powerful). If a field appears on the edit operation, then you have it on the edit screen. It is that simple.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Nic is right but I want to be more clear: If you can press "Edit" and modify the value on the screen that pops up, OR you can hover the field and inline-edit it, that means it is on the EDIT screen AND you have EDIT permissions.There is no other case.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yes, sorry, I was unclear on how I got to "you are probably looked at the wrong screen".
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I just have to keep training people so it's really sticking out in my head haha
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank u all for your answers, But still i am not attaining my results. In the above screen shot my system field(fb overall rating) is not added to the edit issue operation. I also checked it in other issue type screen schemes, still it is not added to any screens of edit issue operations. My requirement is to do some calculations in custom field and display the result in builtin/system field in jira. And it should also be non-editable field. Please help me how to proceed with it.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There's two things here: 1. You have not added FB Overall Rating to the screen you have shown us. Look at the box beneath the list - select it and click add. 2. A calculated field is a different story again. It can be done, but which addon are you using to support the scripting/code required?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi
try with "Behaviours plugin"..
https://marketplace.atlassian.com/plugins/com.onresolve.jira.plugin.Behaviours
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
There's no need for that addon in this case, Peter's answer solves it. Also, the behaviours plugin has been merged into Jamie's Script Runner, so you should be pointing people to that instead. If you install behaviours in more recent JIRA systems, you just get a stub message saying "install script runner"
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
According to Jamie the Plugin is not superseded by Script Runner but still exists in parallel and installation is dependent on the JIRA version which are often enough not updated as quickly in some companies as wished for by admins. Though you are right with "no need" - the plugin is surely overkill for this case here :-)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Er, no. I think your information is significantly out of date. According to Jamie, Behaviours has been merged into Script runner. Since June last year, the marketplace entry is a stub - "This plugin simply installs a servlet that advises that the Behaviours plugin has merged with Script Runner for JIRA."
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.