Tarun Sapra Community Champion

Why are you creating a script for it? what's your use-case as it's generally supported by script runner to create an issue at workflow post-function.

When you want to update an issue you have to put the script in "post-function" . This code should work import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.MutableIssue; if(issue.assigneeId){ // if assignee is empty issue.assignee = ComponentAccessor.jiraAuthenticationContext.loggedInUser; }

Please see my answer and the date format I have used, use that format ( 'yyyy/MM/dd) Your date format is not right. Please correct that and it should work then.

Hello @Stu Since you have script runner installed, you can easily implement these requirements. Please read all the functions available in these 2 links and try them out based on your requirements. http://scriptrunner-docs.connect.adaptavist.com/jiracloud/enhanced-search.html…

You don't need any script for it, you can do it using JQL only status changed TO "In Progress" DURING (startOfMonth(),endOfMonth()) Instead of startOfMonth and endOfMonth you can enter the dates you want. Date format is like YYYY/mm/dd- 2015/05/15

Hello @Francis Peixoto Your assumption is correction i.e. if you execute the JQL fixVersion = <name> Then it should return issues from all projects which have the mention fixVersion. But I am not sure if this approach is scalable because you will have to make sure that different projects have same versions, which over a…

And this related issue is also open -https://jira.atlassian.com/browse/JSWSERVER-5212 

Currently it's not possible to have what you want in JIRA as it's an open issue - https://jira.atlassian.com/browse/JSWSERVER-5614 

Glad that it's working, could you please upvote/accept the answer so that other users with similar issue at hand are helped.

On the scrum board, JIRA considers an issue as done, only and only when the issue has reached the "right most column" in the active sprint view. Thus, make sure the "acceptance test" are in the rightmost column or correctly map their workflow states with columns on the board.

Hello @Pavithra_UST Have you tried the default JIRA functionality "Where is my field" (under the admin tab) on the issue view screen to find out the reason why the custom field (FirstResolved) is not visible any more? Please try that and share the results so that we can troubleshoot further.

Hi @David Hogan Is this working now for you?

I presume the script is using the groovy interpreter, and if that's the case then it's very easy to subtract the days and the get the correct answer. Sample - to subtract 25 days use (groovy.time.TimeCategory) { def date = new Date() println date println date-25.days}…

Out of the box you can't have it, I use the script runner plugin for implementing such features. Samples here https://scriptrunner.adaptavist.com/latest/jira/recipes/workflow/validators/simple-scripted-validators.html You can easily get the value of the date using customFieldManager then convert the value to an Date object…

Hello @Syed Farath Sayeed Can you please share the code snippet which you have added in the vm file and did you restart jira after making the change? And what is the type of your custom field?

Hello @Fabio Manzoni You can implement a check in the "validation" phase. If the user is entering the date on the create screen then you can add a check in the "validation" phase of the workflow transition that the date should not be less than the current date.

Hello @Heather Stoddard Please make sure you have time tracking enabled on the cloud instance https://confluence.atlassian.com/adminjiracloud/configuring-time-tracking-818578858.html And also add the "Time tracking" field to the screens of the issueTypes -> projects. See here…

That's good to know, no wonder it was returning null. As the only reason it can return null is either it's empty(which I was thinking) or it's not on the screen (which is the actual reason). Please accept/upvote if you felt the answer was useful or might help other users.

Can you try "getFieldByName()" https://scriptrunner.adaptavist.com/5.3.9/jira/behaviours-api-quickref.html And also since it's labels field then it will be returning a list of values instead of a single value, may be you have to do "list.first()" to get the first value.

Hello @Rob Schalken Could it be that the script is executed on for the issue which has empty labels because in that case it will throw NullPOinterException.

Hello @[deleted] How are you categorizing the teams in our JIRA instance, are you using any custom fields? LIke if each team has their own board then in the board filer there must be an identifier for the teams like some custom field etc. If you append that custom field clause in your JQL then it should do the trick. 

Awesome!

Here's the KB article explaining how to do it. https://confluence.atlassian.com/jirakb/how-to-remove-the-email-prefix-in-jira-smtp-server-configuration-321848227.html

You can easily add custom fields if you have admin rights. Simple guide here https://confluence.atlassian.com/adminjiraserver071/adding-a-custom-field-802592519.html PS: 'start date in schedule' and 'start date in fact' sounds strange, why not go with "Scheduled start date" and "Actual start date"

As MIrek shared already that it's not supported out of the box. Possible duplicate here - https://community.atlassian.com/t5/Jira-Software-questions/Can-I-use-an-autocomplete-renderer-with-a-select-list-custom/qaq-p/605690

Please accept/upvote the answer so that other users can be helped.

"Dat ziet er heel smakelijk uit" , the cake looks nice!

The top voted answer here should provide an good answer https://community.atlassian.com/t5/Jira-Software-questions/burndown-chart-to-show-story-points-from-sub-task-or-technical/qaq-p/130051

Thanks a lot and Congrats to all!

Out of the box JIRA doesn't support default values for system field. Though you can achieve with various plugins available on the marketplace. The plugin I use is the "Script runner" plugin's Behaviour module. Some samples here https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html