Alexey Matveev Expert

You could remove the Story Point field from the Edit screen. Then you could create a screen with the Story Point field, add a transition with the screen and make this condition only for the users/grups/roles you want. 

Hello, I think you would need an add-on for it. For example, Power Scripts. You can find more info here https://confluence.cprime.io/display/SIL/Email+Templates Or you could use Adaptivist ScriptRunner. You can find more info here: https://scriptrunner.adaptavist.com/latest/jira/builtin-scripts.html#_send_a_custom_email

Hello, I think you can do it with Jira Rest Api. you can find more info here: https://developer.atlassian.com/cloud/jira/platform/rest/#api-api-2-issue-post

If you use a Kanban board then it is the first column in the Kanban board. If you use a Scrum board then when you enter the project you will see the Backlog menu in the left-side vertical menu.

You would need to give more details about the proble. The error, which you get, would enough

You would need an add-on like Power Scripts or Adaptivist ScriptRunner to run a JQL query which would show all stories in the TO DO status and their subtasks are in the In Progress status. For example, if you have Adaptivist ScriptRunner you could use the following query issuefunction in parentsOf("status = \"In…

You should go to Issues->Search Issues. Then you should enter your JQL Query and use the "Save as" button.

You could do it with the following line: import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.MutableIssue MutableIssue issue = ComponentAccessor.getIssueManager().getIssueByCurrentKey("issuekey")

Could you show the script and kindly have a look at the errors in the log file.

I do not know of such a plugin which would let you get the information that you need. But you can get it by using Jira GUI.

Do you want to get this info automatically? If yes then you would need to write a program using Jira Java Api. For example this program in groovy would iterate over all screens and get info about all custom fields. import com.atlassian.jira.component.ComponentAccessor…

You would need an add-on like Power Scripts, Adaptivist ScriptRunner or Automation for Jira. If you had Power Scripts you could create a post-function on the required transition with a script like this %parent%.assignee = currentUser() This script would assign the current user to the parents issue. You can read more about…

You can write a condition like this import com.atlassian.jira.component.ComponentAccessor def currentUser = ComponentAccessor.getJiraAuthenticationContext().getLoggedInUser() return ComponentAccessor.getGroupManager().isUserInGroup(currentUser,"jira-administrators") It would check that the current user belongs to…

If I use the include for three resolutions in a transition in project A's workflow, do I also need to exclude the remaining 12 transitions that don't apply to project A You do not need to exclude the remaining 12 transitions If the answer to that is no, can I use include in some projects and exclude in others? Or does it…

Hello, Resolved is a resolution and closed is a status. Resolution means that your ticket was resolved. It can be resolved as done, declined or something else. Closed means that all work is finished on the ticket. You can query all closed tickets with the following JQL query status = Closed You need to do a transition to…

Hello, You need to add time tracking field to the create, edit and view screens.

I mostly used Adpativist ScriptRunner, Power Scripts and Automation for Jira. You can see prices here: https://marketplace.atlassian.com/plugins/com.keplerrominfo.jira.plugins.jjupin/server/overview https://marketplace.atlassian.com/plugins/com.onresolve.jira.groovy.groovyrunner/cloud/overview…

If you want to make it in a more secure way then do not give the users Jira-software license and they will not be able to use boards.

Hello, By default subtask statuses do not depend on story statuses and vice versa. You would need to use an add-on to make statuses of sotries and subtasks be dependent on each other.

Hello, You would need to setup Jira mail handler for the inbox. https://confluence.atlassian.com/adminjiraserver071/creating-issues-and-comments-from-email-802592933.html

Hello, There is a free plugin called Clone and Move For Jira. The plugin is not available for Jira Cloud. https://marketplace.atlassian.com/plugins/com.ideotechnologies.jira.plugins.clone-and-move-jira-plugin/server/overview

Then you need to create a scripted field with a script like this import com.atlassian.jira.component.ComponentAccessor def cs = ComponentAccessor.getCustomFieldManager().getCustomFieldObjectByName("customfieldname"); return issue.getCustomFieldValue(cs)/40*100

What do you mean that you will use two custom fields for a variable value? one value can be used for one field or there is something else? Basically your script would look like this import com.atlassian.jira.component.ComponentAccessor def cs =…

You can try to use workflow properties. You can read more about workflow properties here: http://www.j-tricks.com/tutorials/permissions-based-on-workflow-status

That is exactly the problem with SQL queries. You should dig yourself into Jira SQL database and find out how to do certain things. In the end your SQL queries will get very large and it will be difficult to support your SQL quieries especially for people who will "inherit" your code. You should use Jira Rest Api to get…

Do you mean that the two tasks are subtasks of the User Story? I just checked it on Cloud. There is nothing wrong with it. You can release only one subtask for a User Story and all other subtasks will stay on the kanban board. I mean you can release the two subtasks in different releases.

I guess there must be a workflow property which restricts editing in the closed status. You can remove the property and you will be able to edit the issue. But it all depends on your requirements: 1. You could remove the property. 2. You could let only a certain group to edit the issue. You would need to set the workflow…

Hello, You would need to use an add-on like Power Scripts or Scriptrunner. You could create a custom validator which would implement your logic. Validators work after you push the submit button. If you want to make your applicaton more responsive then you could use Power Scripts Live Fields or ScriptRunner behaviour. In…

Could you tell more from where you are trying to call the JQL query?

Maybe I did not understand your question but your JQL would look like this "Epic Link" = "IssueKey"