Alexey Matveev Expert

Have a look at the project notification scheme. You should add watchers in front of the required events. You can find more info here: https://confluence.atlassian.com/adminjiracloud/creating-a-notification-scheme-776636401.html

Hello, Issues, which are visible in a Kanban board, are selected by the filter, which is defined for the board. Look at the board filter and make changes to the issue so, that the issue does not satisfy the filter anymore. In this case you will not see the issue in the Kanban board.

Right. It is Browse Projects :)

Hello, Hover your mouse over the Start Sprint button and you will see, why you can not start the sprint.

You can find info on how to verify permissions for a user here: https://confluence.atlassian.com/adminjiraserver071/jira-admin-helper-802593078.html

To let a user to view issues in a project you should give the user the Browse issues permission in the project permission scheme. You need to be a Jira Admin to do it. You grant this permission either to the user or the user group or the user role. It is preferable to grant permissions via roles. You can find more info…

Are you sure that the user, whom you add has right to view the issue?

Hello, When do you get the error? Are you sure that the user can view this issue?

I see. It is Node JS. I do not think you need to change anything.

You can not do it out of the box. But you can develop a listener, which would catch the ProjectCreatedEvent and notify required users. You could develop the listener in your plugin or you could use the ScriptRunner plugin.

What framework do you use? I think you do not have to change anything.

You can see many example in my article here: https://community.atlassian.com/t5/Agile-articles/Three-ways-to-update-an-issue-in-Jira-Java-Api/ba-p/736585

Hello, Try to make a ScriptRunner behaviour if you are not on Cloud. https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html Behaviours can hide field in UI.

{"fields":{"summary":"This is a shorthand for a set operation on the summary field","description":"description changed"}} PUT /rest/api/2/issue/issuekey

Try to log info into the atlassian-jira.log and have a look if it works as you expect. You can log with log.error("variable: " + variable)

You do not need to write a script for the ScriptRunner plugin. You can find an example here: https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html#_example_setting_up_a_hidden_field

You should use PUT /rest/api/2/issue/{issueIdOrKey} not the eidtmeta

It is not possible for Cloud. UI can not be modified in the Cloud version. 

I think if a framework does not let you do something, then you either have to ask the developers of the framework, how to do it, or find another framework. 

Hello, I think you should use Jira Rest Api. There is a search call, which can accept a JQL query and return issues. https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/#api/2/search

Hello, You would need an add-on for it like Power Scripts (Live Fields) or ScriptRunner(Behaviours)

Hello, You can find all info here: https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/?_ga=2.112205060.1476107635.1526884318-593458345.1525875113#api/2/issue-editIssue

Try to use PUT /rest/api/2/comment/{commentId}/properties/{propertyKey} I am not sure which java rest client you use. But you can always use the jersey client.

List<GenericValues>

Да, у меня тоже на мегафоне не работает. Onlime говорят тоже.

You can find an answer here: https://stackoverflow.com/questions/45031475/how-to-create-an-internal-comment-on-a-jira-issue-using-the-jira-cloud-rest-api

Unfortunately, I do not have a demo.

An issue can not be created because of the validator. My idea is to remove the validator and add a behaviour, which will check if the epic link field is not empty. In this case users will be able to create issues via REST API and Mail even if the epic link field is empty.

Hello, You can develop a listener, which would work on the Issue Commented event. You could check the required condition and update the custom field value. Or you could use such plugins as Power Scripts or ScriptRunner to develop such a listener.

You are developing a plugin, are not you? If so, then when you create a custom field type, you must provide vm templates for edit and view. Those vm templates will be shown in Jira UI. Put all your code there. Instead of drawing graphs by yourself, I would use a JavaScript framework.