Ravi Sagar _Sparxsys_ Expert

Hi @Timur Zhamaletdinov I would tackle this requirement in 2 steps - first ask the user quantity (let us say x) and then based on that number create x number of sub-tasks. A bit of a pain for the end user to fill the form in 2 or 3 steps but it will help in reporting later on. Now to create sub-tasks automatically you…

Hi @Ana Bolanos If you don't have Jira Administrator rights then you can use REST API. There is a resource for creating a component. You still need Project Administration rights on those 60 projects. Ravi

Hi @kzander_ Using ScriptRunner for Jira you can look into the ChangeHistory of the issues but that is not the only thing it can do. It will help you to do extreme customisations in Jira. You can evaluate it for free though and get familiar with its features. Ravi

Hi @Rufus Casey You can use the following. labels = labelname or labels in (label1, label2) Ravi 

Hi @kzander_ For created you can use something like this. creator = admin and updated > startOfDay() For some fields you can try something like this. status changed by "admin" and updated > startOfDay("-1") Usually the change history has all the information about who actually did the change and when but to search on this…

Hi @Paul Can you raise this as a bug on ScriptRunner support please? Thanks, Ravi

Yeah I am not old :p If results are inconsistent then try creating a filter for sub queries. The Atlassian documentation says L to R but your truth table says something else. I guess the parentheses are still respected (at least in most cases). 

I love this :) brings back memories. Anyways for without parenthesis column what is your operator precedence - left to right or right to left?

@Swaroop Rao You can follow this issue: https://jira.atlassian.com/browse/JRASERVER-39107 The results should not vary though but Jira does remove nested parenthesis. It is annoying to read your own JQL after few weeks and understand the logic. Try creating filters for your sub queries and use it in the JQL like filter =…

Hi @Sunil Mandalika Here is the code for you. def fixVersion = getFieldById(getFieldChanged()).getValue() def releaseDate = getFieldByName("Release Date") log.debug("Fix Version: " + fixVersion) if (fixVersion.toString().contains("2019-XYZ") ) { releaseDate.setRequired(true) } else { releaseDate.setRequired(false) } Use…

Hi @Matt Marino What you can do is use the following code in Send a custom email listener's Condition and Configuration section. Label added import com.atlassian.jira.component.ComponentAccessor def changeHistoryManager = ComponentAccessor.getChangeHistoryManager() def previousLabels =…

Hi @Carlos David I recently answered a similar question few days ago. Take a look here. You can try something like this. def parentField = getFieldById("customfield_10802") def parentFieldValue = parentField.getValue() def childField = getFieldById("customfield_10802:1") def childFieldValue = childField.getValue() Let me…

Ok so try selecting the link type first and also check the checkbox called map field values. The next screen will ask you to map "is part of" value in your CSV to is part of inward link. Try that.

Hi @Jordan Berry Here is what you can do. First create a REST Endpoint with ScriptRunner. import com.atlassian.jira.component.ComponentAccessor import com.atlassian.sal.api.ApplicationProperties import com.atlassian.sal.api.UrlMode import com.onresolve.scriptrunner.runner.ScriptRunnerImpl import…

Hi @NurTest Are you sure the transition where you have added this validator has been executed? Also did you publish your workflow? Ravi

Hi @Pooja Heda Where did you add the jira.issue.editable flag? It should be on the workflow step and don't forget to publish the workflow. Ravi

Hi @Piyal Nanayakkara If you link Epics and Stories using the Jira Software board the Epic Link field is used. Ravi

Hi @Mihai Mihai Here is the complete code that will check whether the filename is already there in the child task (linked) for not. import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.link.IssueLink import com.atlassian.jira.issue.comments.Comment import…

Hi @Mickael When you add new fields, they are added on the left hand side but with the help of the CSS code I shared above you can visually move them on the right hand side (I guess that's what you wanted). There is no other configurable option to change the layout of the fields. Ravi

Hi @Mujtaba shah Not really. Each portal has its own url (portal/1 or 2 or 3) but not on a separate sub domain (a prefix). Ravi

Hi @Katharina Fenner No there is a free solution as well. You can use JavaScript. Take a look at this link. Please note that this is not really recommended solution, it is more of a hack. For setting simple default description it will work well but the complexity can increase for creating template like solution where…

Hi @PAUL NGONG NJUAKOM Are you on Jira cloud or server? On Jira Server there is a button called Create on top. When you create a new issue it should appear in the Kanban board. Provided the board is based on that project and its filter is configured to display issues in to-do or create status. If you already have issues in…

Hi @Max Berger What are you trying to do? If you can share some details then it will be a bit easier. Ravi

Hi @Tzim You can use Jira REST API. There are end points for modifying user name. There are php based links to get you started. https://github.com/lesstif/php-jira-rest-client https://community.atlassian.com/t5/Answers-Developer-Questions/JIRA-REST-api-in-PHP/qaq-p/530858 Ravi

Hi @Katharina Fenner Take a look at Smart Issue Templates for Jira. It is a paid app but does exactly what you are looking for. If you just want to insert a default field in the description field then ScriptRunner can also do this for you. Take a look at this example. The advantage of using ScriptRunner is that it has…

Hi Marie, Story points is a custom field. You need to add this field to the screen associated with 'tech debt'. Ravi

No lastAttachment is the last attachment of the current issue not the linked issue. Use the same method you used for fetching the attachments but instead of the current issue pass the linked issue object. Ravi

Hi @Shiva Out of the box this kind of report is not possible however if you look at *Average Age Chart*, it is kind of a grouping of issues based on average number of days issues were unresolved. It can be done for hours, days, weeks, monthly, quarterly and yearly. Take a lot at this gadget in your dashboard. Ravi

Hi @Enas Attia There is a an automation rule in SLA called *Keep on top of SLA*. You can use it to check whether your SLA is about to be breached or has breached. Once that happens you can choose to send email. Ravi

Hi @Mihai Mihai How are you fetching the attachments of the linked issues in your code? Ravi