Ravi Sagar _Sparxsys_ Expert

Hi @gabe vid Behaviours are based on combination of project and issue type. This page has information about it. What exactly are you trying to do in your code? Make the instance field mandatory when Issue Type is either Epic or Story? For which project? Ravi

Hi @XAVIER GUYON This file type is meant to be imported into another Jira instance. You can export in xml if you need to modify something in it. Ravi

Hi @Prav Check whether the user has the permission to Schedule Issues in the permission scheme. Ravi

Hi @John Funk @Zach Dimond Why not add a query based on reporter in your JQL to differentiate based on the person creating the issues? Something like this. reporter in (manager1, manager2) or this in case reporter is changed in future. reporter was in (manager1, manager2) This is probably simpler way of doing it provided…

Hi @Fuad Hasanli How are these users working on the issue? Are they tracking time against the issue? What kind of report do you want to extract? Ravi

Hi @Michal Vaněk You have 2 options. Option 1 You can migration from Jira server to cloud but you will first need to upgrade your Jira server to latest version so that it becomes compatible with Jira cloud. As you are on Jira 6.1.3 and it will take few intermediate upgrades but it is still possible and it is probably the…

HI @[deleted] You can also try Workflow Analyzer for Jira app. Ravi

Hi @Fred W You don't need to purchase licence (although you can) for practicing on your local computer. You can get evaluation licence. Anyways. For database I suggest install Jira with built in database. It will be quick. Later you can switch to MySQL, Oracle or PostgreSQL if you want. This link as all the documentation…

Hi @siva Did you try creating issues after removing the scripted field from the view screen? It seems like some problem with the post function. Also share your scripted field code if you want. Ravi

Not sure why it is not working for other files. I tried the same code with txt files. I will check.

No problem. Thanks for sharing the link, it will help others.

Hi @Martin What is your Jira and ScriptRunner version? Ravi

Hi @desarrollo Should be ok but you still need check for compatible apps and do it on test instance first. More details here. Ravi

Hi @Uriel Hassidim I am not sure honestly why it stopped working after upgrade. It could be a problem with Jira as well after the upgrade. You can raise a support request for someone to take a look at this for you. Attach the log files and any browser console errors. Thanks, Ravi

Ok I understand. Is it persistent? Do these 3 lines appear when you refresh the page? Are there any errors in your browser console?

Hi @Houha Amdouni There is an experimental REST API resource for fetching users of an organisation. Ravi

Also check whether the linked issues are outward links or inward links. The code is only checking for outward links.

Is the name of your Issue Link exactly Parent/Child?

Hi @Uriel Hassidim You mean the Summary column displays blank? Is the Summary column added in the filter? Ravi

Hi @Mihai Mihai As @Fran Garcia mentioned use the Issue Commented event. I tried trimmed version of your code and it works perfectly with slight change. import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.link.IssueLink import com.atlassian.jira.issue.comments.Comment import…

@iggirubio As @Deepanshu Natani mentioned check whether you are using the renewed licence keys.

Hi @Kevin Seery You can create a Text Field (read only) and use the following code in the ScriptRunner's Script Post-Function on your transition. import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.util.DefaultIssueChangeHolder import com.atlassian.jira.issue.ModifiedValue //get the value…

Hi @Timothy Ryner Try this code. def values = cfValues['My Multi List']*.value if ( values.contains('Option 1') || values.contains('Option 2') || values.contains('Option 3')) { return true } else { return false }

Hi @bigmadkev I believe it is this one. Ravi

Thanks for sharing :)

Hi @szk-k I believe you can generate app specific password or try using your token that you generate from Google App. Ravi

Hi @Fahad Akhtar Customers only see the tickets they raised or may be the tickets raised by others in the same organisation. You can however create your own permission scheme if you want. I prefer copying existing and modifying it. More information here. Ravi

Hi @Miguel Belen Check the parent issue type's workflow's Done transition There might be a condition there which is checking for the sub-task status and not letting you make that transition. Ravi

Hi @Sandesh Shetty The table name is jiraissue and you can take a look at the schema here. Ravi

Well kind, you don't really assign SLA to component but instead in the the definition of SLA you choose the query (JQL) and the query can be based on any field in Jira, that means you can use components. Time to first repose SLA could be 2 hours or 4 hours based on component 1 or component 2. So basically it is upto you…