Alexey Matveev Expert

Hello, Issues do not belong to boards. Issues are selected for a board by the filter, which is defined for the board. Go to the board configuration and change the board's filter on the General tab.

I think you did not change the Comment Visibility property. Go to System->General Configuration and set the Comment Visibility property to Groups & Project Roles.

It is possible only if you do not manage your users in Jira. For example, you can use Active Directory or Atlassian Crowd. In this case admins of Active Directory or Atlassian Crowd do not have to have admin priviliges in Jira.

Hello, Do you want to select a random issue via a JQL query? If so then it is not possible. JQL does not have such a function.

I think you would need a plugin for it like Power Scripts, ScriptRunner, Automation for Jira or something like this. You can not make the "Copy field value from parent issue " post function work for Epic.

Hello, Comment visibility works the following way: A user can restrict a comment only to a group or a role to which the user belongs. That is why only users, who belong to the Administrators group, can restrict comments to the Administrator group.

You can find an example here: https://scriptrunner.adaptavist.com/latest/jira/custom-jql-functions.html

You would need to develop your own JQL function for this task

Hello, You said that you wanted to find all affected versions. Do you want to find it using JQL? if so then it is not possible. JQL only returns issues. It can not return fix versions.

Where is the sender added to the issue? If the sender becomes the reporter, then you should configure the project notification scheme to send a notification to the reporter, if status changed (generic event).

Ah, I see. You can not read properties from another plugin in a good supportable way.

Hello, When you create an issue in Jira, the Request Type field is not set. That is why the issue can not be seen in the Portal. Try to set the Request Type field for the issue and the issue will be available in the Portal.

There is nothing special to add. You can reference properties like this $i18n.getText("property.key")

Hello, You can make rest calls the same way as in other scripts. For example, like this: https://community.atlassian.com/t5/Answers-Developer-Questions/Making-a-REST-call-using-script-runner/qaq-p/576712

If should set the My Changes field in the User Profile to "Do not notify me". You will not receive any notification if a change was made by you.

If you want to edit the Summary field of an issue, you should use Jira Server Rest Api. PUT /rest/api/2/issue/{issueIdOrKey}

Hello, If you want to have this functionality out of the box, you can remove the description field from the Edit screen and create a transition in the Open status with the Description field. In this case you will be able to edit the description of an issue only in the Open status.

I just tried and I was able to rename the new sprint.

I am afraid the only choice is to end the current sprint and start a new one.

You should go to the Board Settings -> Columns and add a new column. Then you should map a status to the column. You can find more info here: https://confluence.atlassian.com/agile064/jira-agile-user-s-guide/configuring-a-board/configuring-columns

I do not think you can fetch this info without admin permissions

Scripted Fields in ScriptRunner can connect to databases

You would need a plugin like ScriptRunner, nFeed or Power Database Fields Pro. If you want to develop your own plugin, then create a custom field, which would be inherited from the calculated field. Then code database access via jdbc or anything you like.

There are many different plugins. I used serveral of them: ScriptRunner, Automation for Jira, Power Scripts, Workflow Toolbox. All these plugins can solve you requirement. Try them and choose what you like. There are also other plugins. My opinion would be irrelevant in this case since I do not know what skills you have.…

You can find this info with rest/api/2/auditing/record call

Anyone is a built-in group in Jira. You do not need to set it in the global pemission scheme.

Do you mean that you can see these names in a board? Is it a Jira Software project? Could make a screenshot? If it is on a board, you can go to the board configuration and change these steps in the columns menu.

Do you mean that you want to configure another notification permission scheme? If so, then you can create a new notification scheme by copying the old one. Then make changes to the copied notification scheme and associate the scheme with the project. That should solve your requirement. You can read more here on how to…

The problem is that you can change the display name of a custom field only for the portal view. In Jira the display name of a field will still be always equal to the name of the cusotm field. In your case it will be "Text1". The display name is changed for a request type. Portal operates with request types, but Jira…

It is not possible out of the box