Tarun Sapra Community Champion

@[deleted] can you please share screenshot of the custom field.

Hello @[deleted] What are the options of your checkbox custom field just Yes or No , or something else?

Hello @[deleted] Just to add to @Yogesh Mude answer, writing custom validator is also pretty straightforward, please see sample here https://scriptrunner.adaptavist.com/latest/jira/recipes/workflow/validators/require-fix-version-if-fixed.html

Glad to know @Paul_Sorauer that it's working for you, please accept/upvote the answer so that others are helped as well. thanks!

Hello @[deleted] Kanban boards also have a "sub-filter" and thus it could be that you don't see the issues because of the sub-filter https://confluence.atlassian.com/jirasoftwareserver077/configuring-filters-945533960.html#Configuringfilters-(Kanbanonly)Addingasub-filter Can you also share a screenshot of the configuration.

Hello @Paul_Sorauer You are facing this error because in the original code sample, this portion of the code def input1 = issue.fields[input1CfId] as Integer def input2 = issue.fields[input2CfId] as Integer excepts the customFields input1CfId & input2CfId of type "Number" field that's why they are being "cast" into…

Having two similar fields will just create lot of confusion for admins and for users as well, especially while entering JQL queries as both fields will appear in the drop-down.

Hello @jawedshaikh If you have Script Runner plugin installed, then you can achieve it using the following issueFunction in linkedIssuesOf('issueFunction in subtasksOf("key=<your-story key here>")') and type = bug

Hello @Nick Can you please paste the complete code which you are using currently in your instance.

Hello @Alvin Since you want the value to be populated before issue creation thus Behaviours is the option that comes to my mind as well, can you please try this code import com.atlassian.jira.component.ComponentAccessor def affectedUser = getFieldByName("<You custom field name here>") def currentuser =…

Hello @Mark Markov Indeed, if history changes and other permission(workflow etc) checks are a priority then using the IssueServcie is the safest bet which doesn't violate the permission checks as well unlike the issueManager. updateIssue https://developer.atlassian.com/server/jira/platform/performing-issue-operations/

Hello @Alvin In the custom template, use the following snippet $jiraDurationUtils.getFormattedDuration($value) And from your script return (i.e. returned value should be long) which is passed to jira duration utils. return dateValue.getTime() - dateValue2.getTime()

Hello, @Alvin in order to return the value in days, hours etc, it's possible to do that. Just use JiraDurationUtils.

Just a small suggestion, I personally prefer to use customField.updateValue method to update custom field value on Issue instead of issue.setCustomFieldValue because then the "updateIssue" statement is not required. setCustomFieldValue void setCustomFieldValue(CustomField customField, Object value) Sets a custom field…

Hello @Nic Brough -Adaptavist- I also noticed the "Story points estimate" field in a test cloud Jira instance which I have access to, it's a locked field and thus can't be added by an outside Jira administrator. Also in the first screenshot shared by @Michael Heyns it's displayed as an locked field.

Hello @Alvin In your code the statement dateValue.getTime() - dateValue2.getTime() returns long value and you are trying to cast it to "Date" thus you see this error. Instead you should return return new Date(dateValue.getTime() - dateValue2.getTime())

Hello @Shivani Chauhan As Nic already shared that it's currently not possible to add groups as watchers. Please vote here for this feature request https://jira.atlassian.com/browse/JRASERVER-12913

Hello @Christos Moysiadis In the workflow section (if you have admin rights press "gg" and go to workflow section and there at the bottom of the page there is a list of "Inactive" workflows. Thus, you can easily see which workflows are used by projects and which are not.

Hello @Shivani Chauhan Can you please create a separate question for this, as replying on an old thread which already has an solved question would create confusion for the users.

Hello @Heather Stoddard Once the issue has been created you would need to edit them manually as they won't be accessible after the post-function. Though you can edit the summary and description during the creation process. From the docs Create Subtask This function will create a subtask for the issue that is being…

Hello @Tom Arndt You can have Swimlanes based on queries, thus in the configuration choose Queries isntead of stories and in the queries mention the types type = story type = bug type = bug Thus you can have the issueType based swimlanes.

Hello @Pooja From the docs http://www.midori-global.com/products/better-pdf-exporter-for-jira/documentation/dashboards This article describes a powerful method to export Jira dashboards to PDF documents using the Better PDF Exporter for Jira. The resulted PDF files can be shared, emailed, archived, printed or even further…

You can use an generator here https://www.freeformatter.com/cron-expression-generator-quartz.html

Hello @Shrikant Maheshwari For escalation service, you can easily use an cron expression to execute it daily at 6 pm http://javadox.com/org.quartz-scheduler/quartz/1.8.6/org/quartz/CronExpression.html 0 18 * * * This will execute everyday at 6pm

Hello @Joe Charman Glad to know that it's working, please accept/upvote the answer so that others are helped as well.

Even if there is a "Team board" but still it's a just board because all boards in Jira are based on JQL filters and you can combine JQL queries from individual board to create combined team boards All board specific REST APIs here https://docs.atlassian.com/jira-software/REST/7.0.4/#agile/1.0/board

Hello @muhammad_mansoor As per the REST API I don't see a directly correlation of users with Agile boards. https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/#api/2/user-getUser What do you mean by "team boards"? Also you mention tempo APIs But tempo APIs are only for retrieving worklogs, tempo team information…

Glad to know @muhammad_mansoor that it works now. Script runner plugin does have loads of useful JQL functions. If you are satisfied with the answer please accept it so that others are also helped.

Hello @muhammad_mansoor This JQL query is issueTYpe agnostic thus it works across all issueTypes. Can you share the JQL query which you are using. If you want to filter by types then just add that criteria to the above query.

 worklogAuthor = tsapra and worklogDate > startOfMonth() and project = XYZ As you see in the above query you can use workLogAuthor to mention user and workLogDate to mention date , you can also hard-code the date. If you wish to enter date range please use > & < operators with worklogDate field. Valid formats include:…