Tuncay Senturk _Snapbytes_ Community Champion

Hi @Gareth Welcome to the community! You can get custom field value by using the custom field id as below. item["fields"]["customfield_10010"] Here 10010 is the id of the custom field, you need to get the id values for the specific custom fields. Please bear in mind that every custom field might have a different response…

Hi @Jeff Foege Welcome to the community! The condition for inline editing is to add the field to the Edit Issue screen for the screen scheme associated with the Project/Issue Type. You need to check the screen scheme carefully.…

Sorry, I am not an expert on this, but this was the first solution that came to my mind. That's interesting, as it works in my environment.

Did you not forget the square brackets, did you? I already tried in my environment and it worked. ['Priority1'] rather than 'Priority1'

I am not sure but can you try this one? if(priorityVal.equals("Critical")){ labelsField.setFieldOptions(["Priority1"]) labelsField.setFormValue(['Priority1']) } else { labelsField.setFieldOptions(["Priority2"]) labelsField.setFormValue(['Priority2']) }

Hi, Have you tried this REST function? - GET /rest/api/2/issue/{issueIdOrKey}/editmeta Returns the meta data for editing an issue. https://docs.atlassian.com/software/jira/docs/api/REST/8.18.0/#api/2/issue-getEditIssueMeta

Can you share the pom.xml?

Hi @RichardA You can check this link: https://confluence.atlassian.com/jirakb/how-to-audit-license-usage-and-user-activity-in-jira-1005789475.html 

Awesome! Thanks for sharing @Gorka Puente _Appfire_ 

Hello Have you added sal-api dependency? <dependency> <groupId>com.atlassian.sal</groupId> <artifactId>sal-api</artifactId> <version>${sal.api.version}</version> <scope>provided</scope> </dependency>

I think you definitely need to contact the Atlassian support team.

Hi @Yampalla Srinivas Could you please accept an answer (if it was helpful) so that the post will be marked as resolved? Thanks

Awesome! I will definitely promote this @Community Manager .

Hi @Socko-71 You can check Jira plugin for Jenkins. This workflow trigger might help your needs

Hi @Carla Ann Rowland Please try the code below. Calendar myDueDate = Calendar.getInstance(); myDueDate.add(Calendar.DATE, datetoset); Timestamp dueDateTimestamp = new Timestamp(myDueDate.getTime().getTime())

Happy to hear that it has been solved.

Hello @Felix Herrmann Welcome to the community. Internal errors are the exceptions caught on the server-side which are generally unexpected errors. There should be something wrong in the log files, you can't fix the problem by guessing the problem's root cause. It might be a database issue (generally after migration,…

Happy to help :) 

Good point, please try this one return issue.fixVersions.any{it.name.startsWith("WiFi_")} && !issue.subTaskObjects.any{it.summary == "Automated Test"}

Any update?

Hi @Sami Shaik I'm afraid you can't do that with Jira out of the box. You need to use an app that supports working calendars. Best Tuncay

Hi again @David Lopes Leles Have you fixed the problem? If yes, how?

Hi @saiafonua Have you fixed the problem? If my answer was helpful or any other solution worked, could you please identify and accept the answer so that this thread is marked as resolved?

Hello @tejashree avinash aringle You only cropped the beginning of the stack trace, however, it makes sense to include them all as they give us a chance to locate the root cause of the problem. Sometimes a plugin's code might cause such a problem as well as Jira itself. In this case, I only see GH (GreenHopper formerly…

Wow! Finally we figured out the little mistake (*) :) I am glad it worked.

Ok I see, that's because of the asterisk (*) character. Please try this one, return issue.fixVersions.any{it.name.startsWith("WiFi_")} && !issue.subTaskObjects*.find{it.summary == "Automated Test"}

In your example, the issue has no fixversion starting with WiFi, and it has only a fixversion starting with SDN, but it created a subtask using the script below. Is that correct? return issue.fixVersions*.any{it.name.startsWith("WiFi_")} && !issue.subTaskObjects*.find{it.summary == "Automated Test"}

If an issue has fix versions of WiFi_2.7 and SDN_1.4 it creates one subtask. But if it has only SDN_1.4 it should not create a subtask Is this what you want?

If you get any error, please paste it rather than saying above, as there are lots of comments and it became hard to track.

I think you haven't checked my latest script. I already removed that part, you shouldn't get that error. Can you try this one below? Issue issue = event.issue def change = event?.getChangeLog()?.getRelated("ChildChangeItem")?.find {it.field == "assignee"}; if (change) { issue.getSubTaskObjects()?.findAll {…