Nir Haimov Community Champion

Sorry, i used your code and for me it works good. so i don't know why it happens to you. just try to play with the CSS for the elements

Hi @Sridevi, Can you send me the exact code you wrote?

Go to "Add-ons" -> Script Listeners -> Add new item -> custom listener In the field "Event" choose "issue assigned" in "inline script" you have to write a groovy script that will update your customfield with the current assignee.

With Scriptrunner, you can with listener, update customfield with current assignee once assignee set/changed.

Hi, What @Alexey Matveev suggest may not be good for you as it's only for old Jira versions (5.0-5.0.7) and it cost money. Better option will be: https://marketplace.atlassian.com/apps/823187/releasedog?hosting=server&tab=overview which is for newer versions (7.00-7.11.2) and it's free.

Than do the same with attribute "passwordLastChanged" instead of "login.count" and you will get all users who have changed they password (at list one time in their life). remove this list from all users you will get all users who never changed their password

One way that i think of. By SQL, Find all users with attribute "login.count", will give you all users that ever logged in. SELECT * FROM public.cwd_user_attributes WHERE attribute_name = 'login.count' No get all users from select * from cwd_user Now, remove all users with attribute "login.count" from the list of all users,…

If you change the type of the scripted field from "date picker" to "text field" it will give you the result you want. Your code is fine.

Hi, In your dashboard you can add gadget "Activity Stream" This will shows you all activity of everyone in Jira or a specific user in Jira (depends on how you configure it)

Than lets go for another approach. keep your scripted field. at the end of your scripted field, fire event (of your choice). Create a listener that will listen to the event you fire from the scripted field, in that listener just run re-index for the issue fired the event (which is the issue run the scripted field) Here is…

Hi Shlomi, The right way to do it is: Instead of scriptedfield, create regular customfield. Than, in listener, update that regular customfield with the value you want, and inside the listener, after updating the value in the customfield, make re-index. You can't re-index from scriptedfield as it fails and throw exception…

You can create backup xml file from your DEV env, and upload that xml to your LOCAL env (as restore from backup). But you LOCAL env may move slow after, depends on your PC and how many data you bring from the DEV env

No. You just have to know how to use REST API (generally, it's the same with any REST API). Once you know how to use REST API, and you have the address (which i sent you before) than you are good to go. In the document i sent you there is a guide in the beginning that may help you.

Sorry, but no...

Here is documentation for the REST API: https://docs.atlassian.com/jira/REST/server/ and you need this section of the page: https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/#api/2/project

"Transition" is the action when you are changing status. That means, when user change Epic status from A to B (as you describe) here, at this moment do something. This moment call post-function in transition, which sounds like exactly what you are looking for.

With the REST API, a bit of code and in 5 min you find all the projects with default assignee set to "Unassigned"

Yes, But what are you trying to do exactly?

Sorry but no. Scriptrunner run on the back-end, you are looking for a front-end solution so it can't be done from Scriptrunner.

Actually you can do it with JS. Simply call: JIRA.bind(JIRA.Events.ISSUE_REFRESHED, function() { if ($("#status-val span").text() == "Completed") { $("#create_link").click() } }) Make the call from customfield description, the customfield must be visible in the issue view. Make sure how the status really called "completed"…

Add to your "edit" screen, field called "Time Tracking" it'b a build in field in Jira. This will add 2 fields to your screen: * Estimate * Remain You will have the option than, to log your work. Read this: https://confluence.atlassian.com/jirasoftwarecloud/logging-work-on-issues-902499028.html

Hi, This is actually very easy to accomplish with JQL: status = Open AND created <= -14d You can add to it other parameters if you need (project, issuetype, etc...) 

Try earlier version from their aechive https://www.sourcetreeapp.com/download-archives 

Hi @Mark Montminy This will give you your last comment (if you have any comments) Try it, without sleep or any other timing involve. <% def lastComment = com.atlassian.jira.component.ComponentAccessor.getCommentManager().getLastComment(issue) if (lastComment != null) { out << "Last comment: " << lastComment.body } %> 

Hi @Swarna Radha Here is a working code import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.event.type.EventDispatchOption import com.atlassian.jira.issue.ModifiedValue import com.atlassian.jira.issue.util.DefaultIssueChangeHolder def customFieldManager =…

Great! glad to hear it worked out :)

Hi @Hemanshu Sood, Use this as post-function in your sub-task. change this line: workflowTransitionUtil.setIssue((MutableIssue)issue); to: workflowTransitionUtil.setIssue((MutableIssue)issue.getParentObject()); Yes, 211 is your P3 (but actionId and not statusId), and it will work :)

This script will transition your issue. Just change "211" from my code to the action you want in your post function import com.atlassian.jira.component.ComponentAccessor; import com.atlassian.jira.util.JiraUtils; import com.atlassian.jira.workflow.WorkflowTransitionUtil; import…

The complete code for your needs: enableCache = {-> false} import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.Issue import com.atlassian.jira.issue.IssueManager def issueLinkManager = ComponentAccessor.getIssueLinkManager() def issueManager = ComponentAccessor.getIssueManager() def…

Sent you connection request, please approve, otherwise we can't message to each other.