Comments
-
I am not sure if there is a gadget like this. But you can definitely do it it with the EasyBi plugin. Or you can develop your own graphs in an external application using Jira Rest Api.
-
Time tracking fields will be visible on the view issue screen only if they have a value. That is right, there is not Estimation for a Kanban board.
-
The burn up diagram does not depend on the Fix version field. It depends on the Sprint field.
-
Hello, Gitflow is just a conception how to handle development in a team. You do not need anything except git to implement it.
-
Hello, If you want to add time tracking fields to the detail issue view, then you should find the screens, which are used for this issue type as a view, edit and create screens and add the Time tracking field there. Also you can add these fields for the Kanban board. Go to board -> Configure -> Estimation. Set the Time…
-
What do you mean you can not activate? Do you mean that the action does not work, because you never enter the condition?
-
Hello, If you chose if/else condition, then you should add actions in the + icon, not after all ifs and elses. In your first screenshot you added the Edit issue fields action last, but you should add it to each if or else clause.
-
Hello, It is not possible out of the box. You need a plugin. For example, this one: https://marketplace.atlassian.com/apps/1216386/queues-for-jira-service-desk?hosting=cloud&tab=overview
-
[Edited]
-
No, you do not need Jira Software subscription. It will work just fine with Jira Service Desk.
-
You are welcome!
-
Hello, It means that you are not authenticated in Jira. Are you sure that you provide valid credentials for basic_auth? Does your Jira instance use basic authentication?
-
I see. Then you should paste the script either to a post function or to a listener. It depends on how many transitions must use the script. If it is a single transition, it is better to put it to a post function. If there are multiple transitions, then it is simpler to use a listener.
-
Hello, What do you mean by tagging a release version? You mean to set the Fix version field in an issue? Also you asked about a report? What report do you use?
-
It depends on your case. What do you want to do? What is your business requirement?
-
I just asked, where you run the function. You run it from the Script Console and it is fine. It means you do not need a different thread. I think the problem is that transition 11 does not exist for the current status of your issue.
-
Hello, You can do it. It all depends on the process, which you want to have in Jira. Boards just visualize Jira issues, that is why you can always migrate to a Scrum board or a Kanban board. But if you have Jira Software license, I think you should go for Jira software boards.
-
Hello, Do you mean that you want to see to what branch a Jira ticket is linked? Then you should create an application link from your Jira to Bitbucket and connect a Jira ticket with a branch. In this case you will be able to see all connected branches to a Jira ticket in the development web panel in the issue detailed…
-
Hello, Go to the board settings -> columns and have a look what statuses are mapped to the backlog. After you do it, make sure that you have a transition from the TODO column status to the status in the Backlog column. You can see transitions in the project workflow scheme defined for your project.
-
Hello, Try to enable this plugin again and look in the logs. Usually there are helpful messages when enabling a plugin.
-
Hello, Kindly check that the Priority field is added to the Edit screen for this issue type.
-
Hello, Unfortunately, it is impossible to catch the Update Issue Event with Service Desk automation rules. You need an add-on for it. For example, Automation Lite for Jira (it is a free add-on). Or you can use the Power Scripts add-on or the ScriptRunner add-on.
-
@Dean Martinetti It is nice to hear that it worked for you! If my answer helped you, kindly accept my answer. In this case other users will be able to find this answer, if they have a similar question.
-
Hello, Where do you call this script? We had this problem in a post function. We used a different thread to move the issue to a different status.
-
What is the template for your scripted field?
-
You should add opsbar-sequence to all transitions. Otherwise transitions will not be sorted. the ops.bar.group.size.opsbar-transitions you add to the jira-config.properties file, which is situated in the JIRA_HOME folder. And you need to restart Jira
-
Just return $value. Without the longValue() part.
-
Hello, You should find all transitions, which lead to statuss Done and use the Update Issue Field post function to update the value of the Resolution field.
-
Hello, What is exactly the error? The value has a different format on the screen?
-
Hello, To order statuses you should use the opsbar-sequence workflow property: https://confluence.atlassian.com/adminjiraserver071/workflow-properties-802592825.html This solution work for Cloud and Server How manipulate the number of displayed transitions you can find here:…