Alexey Matveev Expert

Hello, You can create a filter which selects your task and then make a subscription for the filter. the Subscription means that a email will be sent to you or a group of users on schedule (you provide the schedule yourself). 

Hello, How come you get 600 goal out of 200 organization? Each organization has only 1 goal, that is why there will be 200 goals? Anyway you could create JQL like this organizations in ("orgName1", ""orgName2", ""orgName3") You would have only 3 JQL goals: bronze package, silver package, gold package.

Hello, It is not possible out of the box. You would need a custom add-on. For example, Queues for Jira Service desk add-on. https://marketplace.atlassian.com/plugins/com.intenso.jira.queues-extension/server/overview

Hello, To get help about keyboard shortcuts: type "?" or go to ?->Keyboard shorcuts To create a new task, type "c"

Hello, You could create two groups for them. For example, normal_customer_group and priority_customer_group. Then you would include all customers to the correct group and when you define SLA you would define two goals with it is own jql query and time 1. reporter in membersOf("normal_customer_group") 2. reporter in…

Try to run the script. I think it is just a static compilation error. If you run it, then it should work

It is just a static compilation error. Do not pay attention to it, it will work just fine

Change atlassian-plugin.xml to <?xml version="1.0" encoding="UTF-8"?> <atlassian-plugin key="${project.groupId}.${project.artifactId}" name="${project.name}" plugins-version="2"> <plugin-info> <description>${project.description}</description> <version>${project.version}</version> <vendor name="${project.organization.name}"…

Change pom.xml to <?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion>…

Hello, could you try "Number field" >= 280040

It is ok. You can use it. Yes, it can change but any Jira API can change but it is still better to use it than to query the database.

Go to the project queue and there must be the Edit queue button. Click it and you will be able to see the JQL query. You need to be a project administrator to be able to see the button. Kindly read more herehttps://confluence.atlassian.com/get-started-with-jira-service-desk/make-queues-for-your-team-917968317.html

Hello, When you add a queue to Jira Service desk you provide a JQL query which selects issues which will be selected by the queue. Check the JQL query for the queue where you want your issues to be and fill the correct fields for the issues.

Hello, It could be hidden by JavaScript or a plugin which lets you hide web items like Adaptivist Scriptrunner.

Make sure that the columns in the Kanban board are correctly mapped to Jira statuses. 

Hello, You should not receive information from Jira database. Use Jira Rest Api instead. https://developer.atlassian.com/jiradev/jira-apis

The problem is that team.getValue(issue) returns List<Group> not a String. That is why you should write like this import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.MutableIssue import com.atlassian.crowd.embedded.api.Group String userName; def customFieldManager =…

I did not check it. But the problem is that you added sal dependency and active objects dependency without the scope parameter which means that these libraries will be packed in your jar and will be used from your jar, which means that they will not be initialized properly and you may have problems. You should use provided…

You added unusual dependencies in your pom.xml for your Active objects. Try my pom.xml. <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> <modelVersion>4.0.0</modelVersion>…

You are a Jira Administrator, you should know all your schemes and make changes keeping in mind the whole configuration.

Hello, You need to change the permission scheme and let only selected by you users/groups/roles see the project. You can create an new permission scheme and grant necessary permissions then you can add this permission scheme to the required project. In this case all other projects will not have any changes.

That is right. If you have no outgoing transactions from a status then you can not add a new outgoing transaction to the status if the workflow is acitve. You need to creata a copy of the workflow, then make all changes to the copied workflow and add the workflow to the project workflow scheme instead of the old workflow.

Hello, Could you provide pom.xml?

The issues which you already closed will not be updated. You need to update them manually. Choose either: 1. If you have Adaptivist ScriptRunner add-on then there is the Bulk Fix Resolutions built in script. https://scriptrunner.adaptavist.com/latest/jira/builtin-scripts.html#_bulk_fix_resolutions 2. You can create a…

You should do either 1 or 2. If you want the resolution to be set manually then number 1, if you want the resolution to be set automatically then number 2. Yes, you should edit the workflow. You can read more in the following link about editing workflows…

You can 1. Add a screen on the transition to the closed status with the resolution field. In this case a user who will make the transition will set the resolution mannually. 2. Add the Update Issue Field post function on the transition to the closed status. In the post function set the resolution field to a suitable value.…

Kindly change your code to Your asset <a href="http://jiraurl/browse/<% out << issue.key %>"><% out << issue.key %></a> has no warranty. And change jiraurl to your jira url

Make sure that a resolution is set for issues in the Closed status. If resolution is not set, then Jira will treat them as open. 

I guess you are using internal Jira database. Kindly read the guide how to execute sql statements there https://confluence.atlassian.com/jirakb/running-sql-commands-in-a-hsql-database-685900390.html

Try something like this Your asset <a href="http://jiraurl/browse/><% out << issue.key %>"><% out << issue.key %><a/> has no warranty.