Ivan Tovbin Expert

I suppose you can do this: import java.sql.Timestamp issue.setUpdated(new Timestamp(System.currentTimeMillis())) This will set the value of 'Updated' field to the current time, which is time of your script execution. 

You'll have to show us your code so that we can check if there's something wrong with it.

Email This Issue seems to be the way to go here. Among other things it allows you to configure custom email templates which can render issue field values in their body. And then you can configure a post function to send an email using these templates.

Could you provide more details about your use case? From your description it looks like you wanna show only those components that have no issues associated with them yet. Aren't you going to run out of "free" components very fast that way?

@Monique vdB 25 pounds is what? ~11 kg? Are you telling me that a board game weighs 11 kgs?! You gotta be kidding me! I imagine it has real loot inside lol?

@Thomas Schlegel no way! Is it also infamous for it's misses on 99% shots that ruin your game lol?

@Monique vdB Is that a PnP game? Something like oldschool Dungeons and Dragons?

XCOM! Gotta be one of the best game series ever! Been a fan since the very first game in 1995. Other than that I absolutely love RPGs.

You can do it by creating a temporary transition from your 'Closed' status right back to itself and then add a post function to that transition that sets a resolution. After that just trigger this transition through bulk edit.

You can do it like so: def issueMgr = ComponentAccessor.getIssueManager() def issues = issueMgr.getIssueObjects(issueMgr.getIssueIdsForProject(projectId)) This will return an Array List of all issues in a project with the given 'projectId' 

No, you can't do that from the UI. This can only be achieved by directly editing some DB entries and any direct tampering with the DB is NOT RECOMMENDED unless you know exactly what you are doing. With that in mind, if you absolutely have to change your starting issue key number I'd do it in a brand new project. Check out…

Check out this documentation on Jira sizing. As for personal experience, for an instance with ~50 projects and ~70k issues we've set JVM heap size to 6GB and are doing just fine.

Hi Stephen, Indeed, you can't do it with standard JSD automation that comes out of the box due to it beeing so limited. With 'Automation for Jira' plugin however, this can be done with almost no effort at all: Trigger: Issue Created Condition: JQL condition Action: Edit issue And of course this can also be done with…

I suppose you can do it by taking away the permission to clone an issue when it's in a 'Closed' status. Check out this documentation for more details.

I think you are going through a wrong channel. You need to contact Atlassian Support if you want to report a bug. support.atlassian.com/contact

Hi Adam, Assuming that at some point in your code you are getting an array of issues returned by your JQL search, you can construct a multi-line string which would list the links to every issue you find and then use that string in your email body, like so: String issueLinks =…

Ah, I see. You didn't mention you meant a 3rd party plugin in your question, so I naturally assumed that we're talking about JSD SLA feature here. Regardless, even though I'm not familliar with 'Enhance for Jira' plugin my guess is that it still stores SLA data in an 'SLA indicator' custom field, which means that you can…

SLA is a feature of Jira Service Desk and thus can only be configured in a 'service desk' type projects. As for notifications you can either use built-in JSD automation to add a comment to the issue (which can trigger a notification) when remaining SLA time is less than 30 minutes OR use Automation for Jira to create a…

Check out this article. It has some tips on creating script files with common code.

Hi Damian, Available buttons have nothing to do with screens. Buttons like 'Resolve', 'Close' etc actually represent workflow transitions. With that in mind I think you just need to simply create a workflow transition from your, say, 'Open' status to 'Closed' and set a condition so that transition would be only available…

Also, check out this documentation.

You shouldn't really use the '=' operator with startOf/endOf functions because resolved = startOfDay() will only return issues that have been resolved EXACTLY at 00:00 of the current day. That said if you want to get all issues resolved since yesterday you need to use resolved >= startOfDay(-1) which will return all issues…

I see. Well I suppose you could store a file in your Jira home directory, which will contain something like: www.someurl.com:12345 And then call that file in your script: def scanner = new Scanner(new File("path to your file")) String urlFromFile while (scanner.hasNextLine()){ urlFromFile = scanner.nextLine() }…

Hi Tyler, You can utilise GStrings to cast a variable into a string like so: def url = new URL("http://${configUrl}:${configPort}".toString()) As for using code from a remote script file check out this article. Hope this helps. 

Hi Ramsay, This will require a rather complex workflow with multiple approval statuses, transitions and conditions, but it's totally possible. First things first though. To make this all work you'll have to somehow tell Jira the title of the reporter. The obvious way to do it, is to create a custom field, which will be…

A scripted post function seems to be the solution here. It will require a 3rd party addon however, like ScriptRunner, JMWE or Power Scripts.

Associating issue types with projects

I'd start here: https://confluence.atlassian.com/jirasoftwareserver/configuring-a-project-938845218.html

Perhaps the reason for this is because the value of a single select list type field is a LazyLoadedOption object and not a string representation of its value. The number you are getting is probably that very option's id.

Perhaps it would be better to set a short name for your field and instead put all that text into field description? It will look something like this: