Alexey Matveev Expert

Hello, You need to grant this user a Service Desk Agent license.

Hello, Unarchive the zip file, then open entities.xml and then find the 11255 issue and try to understand how it differs from other issues in the entities.xml file.

Hello, You can not migrate configuration through a CSV. You can only migrate issues and issue data. Users, permissions, workflows etc is configuration. The only way is to implement configuration manually in Jira.

The problem is that there is no logic for looking for duplicate tickets in Jira because this logic is not that simple. If you want to share access to duplicate tickets manually then you can do it. If you have Jira Service Desk, you can find a duplicate ticket manually in Jira and add any participant you want to this ticket

Try like this: issue in linkedIssues(ABC-123,"clones")

Hello, What is your Bamboo version? 

Hello, Try to use the notification helper to check, if you are supposed to get notifications for a certain event for a certain issue or not. You should go to System->Notification Helper.

Hello, Does you CSV file follow all requirement to a csv file mentioned here: https://confluence.atlassian.com/adminjiracloud/importing-data-from-csv-776636762.html Could you share a screenshot?

Hello, In the OOB Jira you could use the following JQL query: issue in linkedIssues(ABC-123,"clone") This query would show you all cloned issues for ABC_123 issue. This query is not flexible because it shows results only for one issue. If you want a more flexible solution, you need an add-on. For example, you could use the…

Hello Do you follow this guide? https://confluence.atlassian.com/adminjiraserver/sharing-your-workflow-938847433.html

Hello, Could you go to the board configuration -> Columns and have a look to which status the Ready for Development column is mapped?

A webhook is just a program, which fires on an event. It sends to the url you specified a request, which contains a payload inside. There must be your custom service on the other end of the url, which will catch the request of this webhook. That is actually a Rest Call. How to find the webhook payload depends on the…

Hello, It should be : def items = ComponentAccessor.getChangeHistoryManager().getChangeItemsForField( issue, "duedate" );

It is possible with an add-on (your own or any scripting add-on like Power Scripts, ScriptRunner and so on). You could write your own post function, which would look for duplicate tickets, create a link and shared this ticket with the required user.

You are welcome!

Hello, You need to change the workflow, which you use for your issues. You need to add the Blocked and Cancelled statuses. Then you just transtion your issues to the required status.

Hello, You could use Jira Service Desk for it. In Service Desk users publish questions through a protal and by default they can see only their own question. About existing issues. How would you define if an issue exists?

Hello, You should have a look at the atlassian-jira.log file for errors.

Hello, Kanban board was introduced in Jira 7.4 https://confluence.atlassian.com/jirasoftware/jira-software-7-4-x-release-notes-902079634.html You can not use this feature in 7.2.6

You are welcome!

Hello, I think your JQL query should be like this: resolutiondate > startOfWeek()

You could do it with the Power Scripts add-on: https://marketplace.atlassian.com/apps/43318/power-scripts-jira-script-automation?hosting=cloud&tab=overview You could create a validator with a code like this: number[] worklogs = getWorklogIdsForUser(currentUser(),key); if (size(worklogs) > 0) { return true; } else { return…

Hello, You can find info on how register a webhook here: https://developer.atlassian.com/server/jira/platform/webhooks/ 1. You could create one webhook. 2. You will get a payload from the webhook and you will be able to figure out the action and the issue. 3 https://developer.atlassian.com/server/jira/platform/webhooks/

Hello, If your board selects issues from different projects, those users must have the manage sprint permission in all such projects.

That is right. You are not able to filter these issues out because Jira looks from the beginning of the words in the summary field. For example Issue 101 - 41123434 - Something is wrong would work.

The SEN will not be updated, only the license, which you paste in the license box. If you do not renew maintenance , you will not be able to upgrade, even if you do it yourself. Your current Jira license will not let you do it. I do not understand what you mean in the third question. If your maintenance is expired, then…

You need to renew maintenance and you will be given a new license for your Jira.

Yes, correct. Versions are entities of a project, not the whole Jira. Fixed Version and Affected Version fields select versions from the project, to which the issue belong.

Could you give me examples of issues which you can see, but they should not be selected?

Hello, Even if you want to upgrade Jira by yourself, you would still need to renew your license.