Comments
-
Hello, What plugin do you have for writing scripts?
-
You can delete test folder in your plugin. And run atlas-mvn clean install
-
Can you add imports to the class import javax.inject.Inject; import javax.inject.Named; add dependency to the pom.xml <dependency> <groupId>javax.inject</groupId> <artifactId>javax.inject</artifactId> <version>1</version> <scope>provided</scope> </dependency>
-
Hello, You have relative dates in Jira. If you have Server version of Jira you can follow the guide below to change relative dates https://confluence.atlassian.com/jirakb/disable-relative-dates-in-jira-applications-414187622.html If you are on Jira Cloud, you can ask Atlassian Support.
-
You can read more here about creating and sharing a filter https://confluence.atlassian.com/jiracorecloud/saving-your-search-as-a-filter-765593721.html
-
Hello, It returns the real default assignee. When you choose a component on the issue creation screen the default assignee will be set. When you create a component you can set several choices for the default assignee: PROJECT_LEAD, COMPONENT_LEAD, UNASSIGNED. The Rest will return you the real name of the default assignee
-
Hello, Restrictions for a board are taken from the underlying filter. If the filter is shared with a user, then the user will have access to the board. All you need is to create 3 filters and share them with required users. Then you have to associate these filters with the boards.
-
Hello, What do you mean by "new Jira issue view"?
-
I see. About drop down with Windows 10. You can create a single select custom field in Jira. For example, you will call it "OS". When you define a request in the portal you can set any display name for the field. You can give it a name "Which is the environment?" and then in the portal the name will be "Which is the…
-
Hello, 1. You could create a project for each product. In this case you could choose from the the product at the root portal. But in this case agents would have to manage several projects. 2. You can group requests by product names. In this case you could choose a group first and then choose request type. Agents would work…
-
I see. Yes, if you change the filter of the board, then you will have no sub tasks on the board and sprint burndown. That is right.
-
Hello, Do you have any errors in the log file? Try to make this post-function first in the post function list and see the result. If no success, then move it after the saving post function and before reindexing, see the result.
-
Hello, You would need Adaptivist ScriptRunner for it. There are additional JQL functions in Scriptrunner. You could write something like this labels = jira OR issueFunction in subtasksOf("labels = jira")
-
Did you add a behaviour in ScriptRunner? Did you map the behaviour to the correct project and issuetypes? Did you see your log.debug() in atlassian log?
-
In the Jira versions I worked with uuid did not influence on it. If username is the same then the user is the same.
-
If you change the filter, all subtasks will disappear from the board. You post above means that you still need subtasks. Why would you like to hide them if you need them? Anyway you can create a quick filter and paste the JQL query there. In this case you can turn the quick filter on and all subtasks will be hidden, but…
-
If you have a scrum board then after you close the active sprint, all issues will be gone. If you have a kanban board, then you could write the JQL filter for the board like this ..... or (resolution is not empty and resolutiondate < -1w) In this case all issues that have resolution, which were set more than a week ago,…
-
Hello, You can forbid any edit of a resolved ticket. You can add a step property to the Resolved step jira.issue.editable = false
-
Hello, You can create a filter where you choose only not sub-task issue types. For example, issuetype in (Task, Story) or issuetype in standardIssueTypes()
-
I guess you have a scripted field. Then try like this import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.comments.Comment import groovy.json.JsonSlurper import com.atlassian.jira.bc.issue.comment.property.CommentPropertyService final SD_PUBLIC_COMMENT = "sd.public.comment" def user =…
-
Hello, I do not ask why you do not want to store values in custom fields. But it is possible. Develop Rest Api in your plugin and store data in ao through the rest api. You can call your rest api from your velocity templates and pass values of required fields to your rest api
-
Go to issue detail view and there will be project key then "-" and then number.
-
Hello, 1. You can install Jira Service Desk as Add-on to your current installation. You administer Jira Service Desk and Jira in the same place. You do not have to change your current projects. You will create a different project or projects for Jira Service Desk. That is all. 2. If you have Confluence tt is possible to…
-
THe code would be like this. Change IssueKey to your issue key import com.atlassian.jira.component.ComponentAccessor import com.atlassian.jira.issue.comments.Comment import groovy.json.JsonSlurper import com.atlassian.jira.bc.issue.comment.property.CommentPropertyService final SD_PUBLIC_COMMENT = "sd.public.comment" def…
-
Hello, You do not have to do something special. If usernames are the same, then user abc from the second AD will be the same as the user from the first abc. You do not have to configure anything
-
Hello, Could you give more infromation on the error. What exactly does not work?
-
Hello, I am not sure what you are trying to achieve. If you want to develop a custom application, then you can use Jira Rest Api in your java application. If you want to develop a Jira plugin then you should read information here https://developer.atlassian.com/docs/getting-started
-
Hello, Have a look at the post below. You can see how to define if a comment is internal or not. Then you can count internal comments https://community.atlassian.com/t5/Marketplace-Apps-questions/Change-an-internal-comment-to-external-shared-with-customer-in/qaq-p/459389 The required line is def isInternal = { Comment c ->…
-
Hello, There is no such JQL. You can use gadgets. For example Issue statistics gadget https://confluence.atlassian.com/jira064/adding-the-issue-statistics-gadget-720417074.html But you can not export it to Excel
-
Yes, you can do it. The problem is how you store it :) it is not a custom field. But you can call a REST and store it.