Tuncay Senturk _Snapbytes_ Community Champion

That's good news. I'm glad you resolved the problem.

Hi @Ellis Barovsky Welcome to the Community! As @Karan Sachdev mentioned, searching by just the issue number is not directly supported through basic or advanced search. Jira expects the full issue key. I don't think it will be an easy way to search, but you can use Scriptrunner's issueFieldMatch and provide a regexp for…

Ok, another version :) if(type == "Configuration"){ log.info("VERIFICA CFG") def affectedVersions = issue.affectedVersions def versionIds = affectedVersions.collect { version -> log.info("affectedVersion: ${version.name} Id: ${version.id}") version.id as Long } log.info("ITEROU NOS AFFECTED VERSIONS")…

Ok, thanks. I am not sure but here is a suggestion. Change your current code section in CreateIssue.groovy from: if(type == "Configuration"){ log.info("VERIFICA CFG") issue.getAffectedVersions() def myAffectedV=[]; for(version in issue.getAffectedVersions()){ log.info("A ITERAR NOS AFFECTED VERSIONS")…

Hi @karin_hardison Only agents with a JSM license can transition (change status) or reassign the JSM tickets. Collaborators can view, comment, attach files on issues, but they can't change the status or change the assignee. So, if the teams working in JS need to update statuses or assignees in JSM tickets directly, they…

Hi @Isabel Fonseca I'm really sorry, but would you mind formatting your code using code blocks? It’s a bit hard for us to read and understand it otherwise—after all, we're humans, not machines 🙂

Hi @serge calderara Atlassian has made significant changes in Jira DAta Center 10.x, you can check the changelog here. It is likely that the class FileSystemAttachmentDirectoryAccessor has been removed as part of these changes. See this thread, it may help your issue.

Last but not least, I'm glad it worked :) 

Whe you pick a specific field like Due date, Structure gives you a simplified array of history changes only for that field. So you don't need to filter for duedate, you're already only getting duedate changes.That's why history works directly as myArray = history.UNIQUE() For your question regarding the ".to", you're…

Hi @Marc Saisse I think it's best to raise a ticket to Xray support team.

Would this work? WITH myArray = history.changes.filter($.field = "duedate") : WITH previousDueDatesArray = WITHOUT(myArray, LAST(myArray)) : WITH formattedArray = MAP(myArray, IF( $.to = LAST(myArray).to, $.to, CONCAT("~~", $.to, "~~") ) ) : JOIN(formattedArray, ", ")

Hi @nida ergenç If I am not getting it wrong, you're auto-filling the Summary field via post function (from task summary field) in order to create the service issue. Even if you're copying the value into Summary, it must exist on the Create screen of the target issue type in the Service project. Since you said you were…

How about trying to wrap that filter parts in parentheses? (filter in ("10879") ) and ...

That sounds incredible, @Kristján Geir Mathiesen! Love the shots! Just like @Daria Kulikova_GitProtect_io I went to the Grand Canyon last year right after the Team'24 event in Vegas. It was my first time there and I was blown away by the views. It was magical and definitely a moment I won’t forget!

Hi @David Burgdorf It might be due to the filter itself; I mean, there may be a misuse of parentheses. Additionally, try this query to find the possible priorities that issues can have: filter in ("10879") and priority not in (High, Medium, Low, None) order by priority

You're absolutely right @Alexander Gromöller. That's deprecated already, sorry for not taking that into account. Could you try this?import static com.adaptavist.hapi.jira.users.Users.* def allUsers = getUsers().toList() allUsers.each { log.warn(it) } It returns all active users. If you need to filter the users, you can do…

Hi @Alexander Gromöller I would also recommend using the getAllApplicationUsers method from the UserManager service class, as @Fabio Racobaldo _Herzum_ mentioned. The UserSearchService is primarily used to filter users based on specific search criteria.

Wow, looks great! Thanks for the update @Damiao Duarte 

Hi @Michael Manes In addition to what @Christopher Yen mentioned, if you are open to using a free app in the Marketplace, you can try SnapAssign, which allows you to exclude users from specific rules and/or shifts. I am one of the people behind this plugin and am happy to help if you have any questions.

I am quite surprised. Why don't I have one? :)

Hi @Team Systemadministration I don't know of a specific instance that starts an event, but when an instance is started, the PluginEnabled event (com.atlassian.plugin.event.events.PluginEnabledEvent) is triggered. Plugins listen for this event and take action accordingly. You can use this event, but note that it is also…

Hi @Damiao Duarte As far as I know, there’s no official public REST API for license usage in Jira Server. You can get that data directly through UI by this URL: /plugins/servlet/applications/versions-licenses however I won't suggest parsing the HTML for sure. You can use Java API to get those counts, hopefully this will…

Hi @Gomez, Jorge (J.) I agree with @bill 's point—it definitely sounds like an automation rule or post-function that’s acting with the reporter as the actor. One other thing worth checking: if you're using ScriptRunner or any other marketplace app that modifies issues, it's possible a script is running in the background…

this is the version with id values that I tried POST: /rest/api/3/bulk/issues/move { "sendBulkNotification": false, "targetToSourcesMapping": { "TMP,10050": { "issueIdsOrKeys": ["TMP-21"], "inferClassificationDefaults": true, "inferFieldDefaults": true, "inferStatusDefaults": true, "inferSubtaskTypeDefault": true } } }

Hi @Denis Rousselle Have you considered using the issue search and Bulk Change in the UI to move/change their issue type? Is the 1.000 issues at a time the reason why you preferred to do them using REST API? Anyway, I was able to run it successfully with the json payload below. But, bear in mind that it has to be POST not…

Hi @Cedric Franken Creating custom Built-In Scripts, (Canned Scripts), in ScriptRunner involves implementing the com.onresolve.scriptrunner.canned.CannedScript interface. However, this interface was not originally designed as a public API, and its documentation is very limited. The link that you provided, also…

Hi @Devika Assaram As @Valerie Knapp stated, Jira allows only user-based assignment, not a team-based assignment. If you want visibility over which team owns the issue, one workaround may be to use a custom field to store the team within the issue.

Hi again, Now, that's weird. I was expecting issue updates to be the reason of SLA recalculation but in your case it seems, recalculation causes issue updates. Is there any paused condition in your SLA definition? Pause condition might cause updating due date continuously, each minute in paused condition means due date is…

Hi @Cindi Miller (she/her) Time to SLA recalculates the SLA Due Date on every issue change, and this behaviour is by design. There are a couple of reasons for this: Jira Cloud event listening is broader: the apps' listeners can only listen generic events like issue created, issue updated, issue transitioned, issue…

Hi @preznicek As far as I know from is a reserved keyword in Python, so you may not access it directly as an attribute using item.from Instead, can you try something like the one below? for history in changelog.histories: for item in history.items: if hasattr(item, "from"): print(f"item.from: {getattr(item, 'from')}")