Alexey Matveev Expert

Hello, Could you explain more what you mean hidden(marked as done)? A screenshot would be great.

No, you can not generate an issue id or change the issue key. You can add a new field with your custom logic

I would add a new column and mapped the status in the same column to this new column

Hello, Go to the Project settings -> Screens. Find the view screen for the HelpDesk issue type and make sure that the Participat field is added to the screen. Also you can push the Gerer button (I guess it is the Admin button in english) and choose the Where is my field button. Then enter the Participant field there and…

Hello, Make sure that there is a transition from the current status of the issue to the status, which is mapped to the column, to which you are trying to move the issue. You can open the issue detail view and see, if there is a button, which lets you do this transition.

You are welcome!

Hello, You should Copy the default permission scheme, associate the copied permission scheme with the project and edit the copied permission scheme. If you edit the default permission scheme, there is a a huge change, that the default permission scheme is associated with another project. That is why permissions will change…

You are welcome!

Hello, You should not delete the bocked by linkage. In this case you will be able always to see blocked issues

Hello, It is not possible. The author of a a version is not stored.

It would be nice to see a screenshot of such notification.

There is no such option as to receive notifications as a creator. Have a look at your project notification scheme. Maybe you are in a group or a role, which is defined for notifications.

You are welcome!

Hello, Unfortunately, I do not know any such plugin for Cloud. There is for Server, Data Center: https://marketplace.atlassian.com/apps/1212137/insight-asset-management-for-jira?hosting=server&tab=overview

Hello, You should define first why you receive notifications. If you receive notifications because you are a watcher, then you should remove yourself from watchers.

You are welcome! If you feel like your question is answered, kindly accept this answer. In this case people with a similar question will be able to find this answer.

You are welcome!

If I answered your question, kindly accept this answer. In this case other users with a similair question will be able to find this answer.

Yea, that is what I meant. Just call these transactions differently and add conditions that only admins can execute these transactions.

Hello, Is it a subtask issue type?

Hello, You can use Java Script for it. But it is not a mantainable solution. Or have a look at plugins. For example, like: https://marketplace.atlassian.com/apps/1211608/color-custom-fields?hosting=server&tab=overview

It depends on what you want to do. If these issues have something in common (a value in a custom field), then you can write customfield = value. If they do not have anything in common, then you can write: issue in ("x", "y")

Try to do like this @ExportAsService @Named public class MyPluginService extends AbstractService { private final SomeHelloWorldInterface helloWorld; @Inject public MyPluginService(final SomeHelloWorldInterface helloWorld) { this.helloWorld = helloWorld; } @Named public class SomeHelloWorldClass implements…

Hello, You would need to create a fliter to select required issue. Then you can add the Filter Results gadget to the dashboard and select there your created fileter.

You are welcome!:)

Hello, Do you want a user to be able to create a component or choose a component from a list of components? If you want the user to create a component, then you have to give Project Admistrator permission to the user. If you want a user to edit an issue, the user must have the Edit Issues permission in the project…

You are welcome!

But if you have a look in the logs, you can find all names for the field. It will help to solve futher problems

https://itc-cloudio.atlassian.net/rest/api/2/search?jql=project="RUT"&maxResults=100&startAt=101

Hello, Try to log the contents for the changelog to the atlassian-jira.log and have a look what is inside the object: log.error("event?.getChangeLog(): ${event?.getChangeLog().toString()}")