Видео

Hi, sorry for keeping you waiting! Thank you for sharing your thoughts on this, we're taking this piece of feedback into consideration for future improvements. If you want to share further details on this or make other suggestions on what you'd like to see from us, we'd love to hear from you on our Nolt board: scriptrunner-for-jira-cloud.nolt.io/

Sorry about that! Please try this link instead, and we'll update our video description also: library.adaptavist.com/entity/Limit-issue-types-based-on-groups Hope this helps 😀

@@scriptrunnerhq Thank you much.. yes that helps.. If I want to have multiple groups in a role then role = "roleName" or I have to include groups role = "Developers", "mm Rest". or role = have to be 1 group only?

@@mdmonn To provide you support for your specific use, our team are ready to help. If you can please raise a support ticket here, we can explore this with you: the-adaptavist-group-support.atlassian.net/servicedesk/customer/user/login?destination=portals

Hi, we hope this script might be helpful to you: library.adaptavist.com/entity/hide-fields-with-no-values?tab=cloud If you need more information, our support team are ready to help; please raise a ticket here: the-adaptavist-group-support.atlassian.net/servicedesk/customer/user/login?destination=portals

Hi, you can achieve the same outcome on Jira Data Center, but you'll need a slightly different approach, try these in-app library scripts: "Set a default option on a cascading select list" and another called "Set Behaviour Hidden". You can also check out some of our documentation for additional support: Setting Field Defaults - docs.adaptavist.com/sr4js/latest/features/behaviours/behaviours-examples/setting-field-defaults Scripted Conditions - docs.adaptavist.com/sr4js/latest/features/behaviours/behaviours-examples/scripted-conditions Hope that helps!

Hi, if you can please raise a ticket here, our support team are ready to help you out today: the-adaptavist-group-support.atlassian.net/servicedesk/customer/user/login?destination=portals

Hi, could you please confirm that you changed the Custom Field IDs to match the fields in your instance? If you have, could you check for any error messages? If there are no error messages, our support team can help if you raise a ticket here: the-adaptavist-group-support.atlassian.net/servicedesk/customer/user/login?destination=portals

@@scriptrunnerhq I managed to make it work, was a mistake in the group name. I had a question though, what happens if ever there is an update on scriptrunner or Jira itself? Will this affect my code and stops functioning?

@@Narsh-xr6sq OK great! No need to worry; version updates won't impact any code you're running.

@@scriptrunnerhq Thanks! And thanks for the demo too!

Hi, we've got it here for your convenience and it's soon to be added to our script library too! // Note: You should run this script by selecting "On load" in the check box above. const ticketDepartment = getFieldById("customfield 10205") const userRegion = getFieldById("customfield 10206") const ticketCat = getFieldById("customfield 10207") const priority = getFieldById("priority") const issueTypeField = getFieldById("issuetype") const user = await makeRequest("/rest/api/2/myself"); const { accountId } = user.body; const userGroups = await makeRequest ("/rest/api/2/user/groups?accountId=" + accountId); const groupNames = userGroups.body.map(({ name }) => name); const group = "Example Group"; if (groupNames.includes(group)) { ticketDepartment.setVisible(false) userRegion.setVisible(false) ticketCat.setVisible(false) priority.setReadOnly(true) }

@@scriptrunnerhq Thanks, I'm testing it right now

Hi, no problem! Let us know which script from the video you're looking for and we'll make sure to share it here for you :)

Thanks Andrii!

Hi! We would need more information about the errors you are encountering. If you can, please raise a ticket through our support portal here: the-adaptavist-group-support.atlassian.net/servicedesk/customer/user/login?destination=portals and someone from our team will help you.

@@scriptrunnerhqThank you for your response. I found out what was the problem, I configured my field to be required trough field configuration, so I guess when that is setup you can't toggle it after using script runner.

Hi @mesonparticle, If you are running a script from Automation for Jira, the issue itself is passed through as a variable. You can check this with the little blue '?' at the bottom right of the script editor. If you click that, you will see a list of variables that are available to you from the area you are writing code for. In this case, the issue is passed through under the "issue" variable. So, the following would work as an script from Automation for Jira: issue.update { setDescription('Automation for Jira') } Hope this helps! - Bobby

Consider us humbled 😅 Thanks for the feedback, we'll share this with our team. If there's an example you'd like to see please let us know; we'd love to write something up!

Hi Tom, thanks very much for that feedback, we’ve passed it on to the product team on your behalf. If you’d be open to it, we’d love to have a chat about the feature and ScriptRunner for Jira Cloud in general. Please reach out to us at customersuccess@adaptavist.com: we’d love to to schedule a call with you if you’re interested!

Hi Jagadeesh, you will need to create a validator in the create transition. To get support with this, you can raise a ticket and a member of our team may be able to assist you: bit.ly/3P8dxEo Hope this helps!

Hi Alok, we’re very sorry for the delay in getting back to you and to hear that you’re having an issue creating scripts - let’s change that! To turn your ScriptRunner experience around, we’d like to set you up with our Customer Success team, where you can get more one-on-one help with your Jira instance. Please email our team here to arrange a call: customersuccess@scriptrunnerhq.com