Comments
-
Hello, As far as I know Pipelines are available only for Bitbucket Cloud
-
Hello, You could use Power Scripts for the task. You could create a file called jqlRecentlyUpdatedSubtasks.sil with the following code: string [] keys = selectIssues(argv[0]); string [] ret; for(string k in keys) { for (string subTaskKey in subtasks(k)) { date recentlyUpdated = currentDate() - argv[1];…
-
Hello, You would need an add-on like Adaptivist ScriptRunner or Power Scripts. If you have Adaptivist scrptrunner you could write a JQL quiery like this (Team = "Team Self Service" AND status not in (Closed,Done,Resolved)) or (issueFunction in subtasksOf("Team =\ "Team Self Service\" AND status not in…
-
SLAs are assigned automatically if your created ticket satisfies SLA's goal. You can not assign manually
-
You could use Adpativist Scriptrunner or Power Scripts add-ons. If you use Power Scripts, you could use Live Fields. You can read more here: https://confluence.cprime.io/display/TR/UI+Manipulation You would need to use lfAllowSelectOptions(field, options[, triggerChange])
-
Have look at UserManager https://docs.atlassian.com/software/jira/docs/api/7.1.7/com/atlassian/jira/user/util/UserManager.html You can get the class by ComponentAccessor.getUserManager(). You could iterate over all users using(I did not check the code though)…
-
It means that you have to define multiple SLA's. When a ticket is created then it will be assigned all SLA's which satisfy the ticket by SLA's goals. And then you will see multiple SLA's ticking for the ticket. Do you have a different behaviour?
-
Hello, You could also use Power Scripts add-on. Power Scripts has Live Fields which are similair to behaviours in ScriptRunner. You can read more here: https://confluence.cprime.io/display/JJUPIN/Live+Fields Or you could also write a validator using Power Scripts. You can find more info here:…
-
It is possible. If a ticket satisfies multiple SLA's then you will see all the the SLA's in the ticket detail view.
-
Hello, You would need an add-on like Tempo Planner. https://marketplace.atlassian.com/plugins/com.tempoplugin.tempo-planner/cloud/overview
-
Try like this { "fields": { "project": { "key": "TRAIL" }, "summary": "san2_bug12", "description" : "desc", "priority": { "id": "1" }, "issuetype": { "name": "Bug" } }, "customfield_10101" : "custom" }
-
Hello, What is the type of your custom field?
-
reporter not in membersOf("")
-
If you have Jira Software, you can create a board and set Swimlane to Epics. Or I guess you would need a plugin like Structure to add such a gadget: https://marketplace.atlassian.com/plugins/com.almworks.jira.structure/server/overview
-
Hello, You do not need to install Scriptrunner, if you want to write your own plugin. You should useEventType.ISSUE_CREATED_ID. You can find more info here: https://developer.atlassian.com/server/jira/platform/writing-jira-event-listeners-with-the-atlassian-event-library/
-
I think you can not do it out of the box. You could install a plugin called Auditor for Jira https://marketplace.atlassian.com/plugins/com.plugenta.jiraauditor/server/overview
-
It must be def param1 = "account-authn" def param2 = "access" def param3 = "1.5.0" def myQuery = "description ~ \"" + param1 + "\" AND description ~ \"" + param2 + "\" AND description ~ \"" + param3 + "\"" log.error(myQuery) def query = jqlQueryParser.parseQuery(myQuery) Kindly check in the logs that myQuery is correct
-
Hello, I am not familiar with Nuxeo. But usually all kind of clients are written to make rest calls easier. These clients hide real calls to REST API. That is why I think you do not need it as long as you know the name of REST API methods. From ScriptRunner you could call the methods either by using HttpUrlConnection:…
-
Hello, You can do it the Power Database Fields PRO. It is called Dynamic queries. Kindly read here https://confluence.cprime.io/pages/viewpage.action?pageId=6556967
-
You can edit comments manually or write a script
-
You need to add the problemField to the behavour (add field) and set the script for the field. In this case the script will fire all the time the problemField changes.
-
Yes, you can do it. You need to add the field, which value influences the other field, to the behavour and put your logic in the script for the field
-
You can not do it with behaviours. You could do it with JavaScript but I would not do it.
-
I do not hink it is possible. Actually there is only 1 comment field and it is not linked to any tab. You can see it in the html code. That is why you should link behaviour to tabs and if a tab is activated you should hide or show the comment field depending on your logic. But it is not possible to link behaviour to a tab.
-
Have a look at jira installation directory. There is a bat file where the name of the service is defined. Change the name of the service and run the bat file.
-
Hello, You can view the History tab in the Detailed Issue View. But I guess it will not be convenient for you to enter each issue. You could create a custom plugin report. https://developer.atlassian.com/server/jira/platform/creating-a-jira-report/
-
Hello, You can not do it out of the box. What you need is to group issues by assignee, not to order them. JQL does not have group by function.
-
You can find an example here https://developer.atlassian.com/cloud/jira/platform/rest/#api-api-2-issue-issueIdOrKey-put
-
Hello, If you use Service Desk then you could make your client Customers and they would be able to log only to the Service Desk portal and read only shared comments. If you you want your client to log in to Jira then you could restrict your comment visibiltity when you create a comment. You can read more about comment…
-
You can change the project workflow scheme after the project was created or you can use Create With Shared Configuration. In this case the new project will have the same schemes like the parent project.