Pierre Ibrahim Insider

Hi James, Surprisingly enough, I now get the same number of rows with Cancelled vs. CANCELLED. Guessing JIRA needed some time to index?

Ah thank you so much for the detailed write up! I was not aware of the jira:entityPropertySet manifest, but that makes sense to start with that as opposed to the jira:entityProperty to avoid the limit altogether. And yeah as far as hitting that API endpoint, I'm just doing it via JIRA Automation rules (for ongoing support)…

Hi Germán, Thank you so much for your detailed answer. I noticed when I was creating the app there's a forge pricing document, just wondering since the app would only be indexing attributes, not reading nor writing anything regularly, would there be any cost incurred? I'm having a difficult time using their calculator as…

Hi Alex, Your explanation makes perfect sense, I'll keep it in mind for the next validator I need to write, or in case the one I did end up writing starts acting wonky. After a lot of trial and error I ended with the following script that seemed to work in all cases: if (issue?.customfield_14690?.value == "No") { //…

Hi John, Unfortunately there is not, no. Reason being is the repository space is just that, a reference for us internally to use when trying to figure out stuff about a client, or just use as a general reference. The client space itself is where all the client work is done, so there's no one work item from the client space…

Found the issue! I needed to do an "exists" check on the inwardIssue before line 15's IF. The corrected code is below: def eventIssue = Issues.getByKey(issue.key as String) def newDeploymentPackageVersionNumber = eventIssue.getCustomFieldValue("New Deployment Package Version Number") def deploymentPackageVersionNumber =…

Thank you so much for your response @Ethann Collins ! Decadis also confirmed this via a ticket I sent their way. I appreciate your insight!

I was able to figure out the correct syntax, it's: %{toString(fieldValue(%{issue.cf10508}, issuesFromJQL("key = " + jiraExpression("issue?.customfield_11257"))))} Thank you again @Sergio García-Consuegra _Decadis AG_ , greatly appreciated! 

One last question if I may @Sergio García-Consuegra _Decadis AG_ , The field I'm trying to copy is a date field, this is the expression right now: %{fieldValue({issue.cf10508}, issuesFromJQL("key = " + jiraExpression("issue?.customfield_11257")))} I've tried surrounding the field in a dateToString() like so:…

This is awesome! Thank you so much Sergio!

@Sergio García-Consuegra _Decadis AG_ this works great! Anyway to get a specific field value from that JQL? I tried the fieldValue() function but it doesn't seem to like taking an issuekey

Hi @Lucas Knorr Essentially what I'm trying to achieve here is I have a task that has the issue picker field, that task has a transition that spins up a subtask with field values from the issue picker field's values. I have a post function that copies field values from the issue picker's issue into the task triggering the…

Hi @Nacho Moreno Ortega , The first phase of the migration will not have any of the same project keys from DC in cloud. I am going to be cloning the projects in DC so that I keep the same config (with no tickets/work items) (maintaining the same workflows, workflow schemes, screens, etc...) Move those to cloud in the…

Thank you for your response, @John Funk ! Greatly appreciated. That shouldn't be a problem as we're keeping the statuses the same across both DC and Cloud, we're merely just recreating the scriptrunner/JWT/JSU validators and post functions that don't seem to make it to cloud.

Hi Bobby! Thanks again for the explanation, greatly appreciated! While this didn't directly solve the issue and I'll explain why, you made me realize what my actual problem is :) So the listener is supposed to listen for multiple fields to change, once it finds that, it increments a counter, that counter is then used in a…

That worked amazingly well! Would you mind explaining a bit what the setEventDispatchOption does? Also to address your concern, I'm using the resulting field from the listener (the counter getting updated) to use in an automation. In one of my earlier iterations in the script, it wasn't auto firing issue updated events…

Hi @Bill Sheboy Thank you so much for taking the time to respond, greatly appreciate it! The rules' purpose is to copy fields across an issue's subtasks, the fields the rule is listening for are fields the team wanted copied across subtasks (and from subtasks to siblings/parent tasks, thus the 4 automation rules mentioned)…

Closing the loop on this, I reached out to Votazz support (the current developer for the currentProjectFunction) and they confirmed that with the Jira server end of life, they are no longer supporting the currentProjectFunction and have indeed pivoted the plugin to the WFH - Daily Wellness Monitor plugin.

Hi @Charlie Misonne , I found it through googling the developer, but interestingly enough, since our prod environment is not updated yet, going to manage apps and looking at the currentProjectFunction add on shows me the following I'll talk with my support team about the JQL Booster Pack, problem being a lot of our filters…