Case Use: We create our issues from Salesforce, using the ServiceRocket connector. ServiceRocket, after years of it working, now states that any field that's mapped in the connector has to show up on the create screen in order to properly create the link back to the SF case. In order to accomodate that, we need to have the task and sub-task fields on the create screen *somewhere*. We do not want people to be able to edit these if they create an issue through Jira. We want all the issues to be created through SF. The only way I can think of to make this work is to have the fields be there, but hidden.
Any help with making this strategy work, or an alternative would be appreciated.
I don't know if after all this time you still got this problem, but i will give it a try.
1st - You can add your fields to a certain screen, let's say the 'Create Issue' one, and configure them to be hidden. This way the users cannot see the field in the screen but cannot change the values as well, for this you need the second part.
2nd- you'd probably need a plugin for this one, with Automation Lite for example, you can make simple tasks and simple triggers for free. You can create a condition that "when an issue is created" and "if a field value is 'X' " then "your other field is set to Y". The field that you defined as hidden, can be called and changed.
You can't show it on Dashboards or on the screens, but it's useful if you need a specific filter that calls that hidden field value.
Hello,
I know two plugins, which can do it: Power Scripts and ScriptRunner.
If you want to use the Power Scripts, you could use the Live Fields feature:
https://confluence.cprime.io/display/JJUPIN/Live+Fields
Just add a script like this as a Live Field:
lfHide(
"customfield_10201"
);
10102 is the id of the custom field, which you need to hide. You can find this id, if you go to cog item -> issues -> custom fields. Then find your field and push the Configure button. You will see the id of the custom field in the url in your browser
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
JIRA doesn't allow you to hide fields. A work-around would be to put those fields on a separate tab on the create screen with a tab label of Do Not Edit. JIRA sees the whole create screen as one so the fields will be there. The tabs are for human use to logically group fields.
There may be a plugin or scripting solution I'm unaware of.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.