Alexey Matveev Expert

the anonymous user is a built-in "user". You do not need to add it to global permissions. the anonymous user means that the user does not log in to Jira. If you want to automate functions, you can distinguish between logged-in user and not logged-in. I never used anonymous user. The problem is that you will never know who…

You can permit the anonymous user in the project permission scheme. It means that the user will be able to see the project and do actions even without logging. But all actions will be taken from an anonymous user. You will not know who exactly the user was.

You can also check this way. If you login to Jira and choose the dashboard menu, then you will see the version of your Jira in the footer of the page. It means that you are on Server.

Look at the link if it contains .atlassian.net then it is Cloud. 

Hello, You need to open all issues of the old assignee in the Issue Navigator with a query like this: assignee= oldassigne Then bulk edit the issues by changing the old assignee to the new one. You can read more about bulk edit here:…

This built-in function let you export configuration of ScriptRunner items so that you could inculde these itmes into a plugin, which will install all these items on adding the plugin to a Jira instance. You can read more about it here: https://scriptrunner.adaptavist.com/latest/jira/creating-a-script-plugin.html

If you want to change an assignee by using this KB, then you have to connect to the Jira database and make changes by executing SQL queries in the KB. If you want to automate the process (it is not only once done job), I would not advise you to use the KB. Better develop a plugin or use available plugins to accomplish this…

Boards do not own issues. Issues appear on the boards by a filter query, which is defined for the board. You define the filter for a board in the Board configuration. Just make sure that the second board filter selects the required issues and the issues will appear in the backlog. But there can be a problem. If an issues…

@Matthew Lane That is how it is done. You can determine which tickets affect the release by a JQL query like this: affectedVersion = 18

Hello, when you add a link it does not mean that you delete the old link. And if you see only the subtask link, it means that you script works before the link was created.

In Jira 7.4 a project administrator will be able to change screens, used in the project under the following conditions: - The screen must not be a default system screen. - The screen must not be shared with any other projects, or used as a transition screen in workflows. - The project admin can add, remove and rearrange…

Releases will only inculde issues which are linked to the Release with the Fix Version field. the Affected version field just shows that the bug can be reproduced in this version. It does not mean that the bug is fixed in this version.

There is a resolved ticket in Atlassian support. There is a workaround. Kindly try to apply the workaround: https://jira.atlassian.com/browse/JRACLOUD-67475

I guess, you script works on the initialization of your behaviour. Add the Date Picker field - Started to the behaviour and add this script to the field.

What kind of calculated field?

I am not that much experienced with Atlassian Crowd. But basically it has the same functionality as Microsoft Active Directory (of course not exactly like Active Directory). That is why, if you import all your users to Jira from Atlassian Crowd, then you can make your requirement work. You can set admins for Atlassian…

@Thomas Deilernice article. I wish I could bookmark this article.

There are two types of integration testing Jira: wired tests and "gui" tests. In the wired test you test all services, which are exported by your Jira plugin. You can find more info here: https://developer.atlassian.com/server/framework/atlassian-sdk/create-and-run-traditional-integration-tests/ In the "gui" test you test…

You would need a GIT server like Bitbuket, GitHub or something like this. If you have Bitbucket, then you can create an application link to your Bitbucket server. If you do not use Bitbucket, then you can use a plugin. For example, this one:…

You should go to the server, where you jira is installed, and open the file.

К сожалению, у меня нет времени писать эту функцию.

You do not need to change the plugin descriptor

Kindly check if the user has the browse issues permission through a role, group or user in the project permission scheme. You can find more info here: https://confluence.atlassian.com/adminjiracloud/managing-project-permissions-776636362.html Or you can open an issue from the project as an admin and choose…

Let's say that a Rejected ticket means that the ticket was transitioned from the Resolved status to the Accepted status. In this case you could write a JQL query like this: status changed from Resolved to Accepted and status = Accepted

Hello, You can open the cog wheel (see the screenshot below), and if you can see such items as Issues, Add-ons, System, then you are an admin. To assign project to team members, grant the assignable user permissions to the team members in the project permissions scheme. You can find more info here:…

Kindly have a look at the Nfeed plugin.

You can not do it out of the box. If you do not want to buy a plugin, then you can write your own plugin. You would need to create your own custom field. You can find more info here: https://developer.atlassian.com/server/jira/platform/creating-a-custom-field-type/

I think you should look in the log file for errors. The log file is in JIRA_HOME/log/atlassian-jira.log

Hello, I do not think such a plugin exists. There is a similiar plugin for IntelliJ but the latest version of the plugin is dated to 2015. https://plugins.jetbrains.com/plugin/2190-atlassian-connector-for-intellij-ide I actually never used the plugin. If you have Bitbucket then you can make an application link with your…

It does not matter what you set - a custom field or the assignee field or the reporter field. You still need to make the data appear in the indexes. And in order to do it you need to execute certain functions. The order of the post functions does not have any influence on the sub-task, because all the functions in your…