Tarun Sapra Community Champion

Hello @Christopher Jaksch The JQL query which you have shared uses the "was" operator, this will result in all the issues which were "failing test". Let's suppose 2 weeks ago issues were failing but now are passed. May be that's what the requester @Kory Zhu wants, to basically query all the issues "historically" but if…

As stated in the docs "By default, project administrators can add agents from other projects to the project. JIRA administrators can add anyone to the project." Thus, if you have project administration permission then you can add other users as agents and it definitely doesn't mean that your own admin account will be…

Stay away from JS based customizations it's toxic! You can use Behaviour module in the Script runner plugin.

You can use the "Customer request type" field in JQL to fetch JSD tickets by request type. From the docs Customer Request Type values follow the format of " projectkey/lowercased-form-title-hyphenated", so it may be possible to guess. For example project key of "ITS": * General Assistance = its/general-assistance *…

Hello @Kory Zhu Since you mention that "As fail testing is a status in Jira not a field" thus if it's a status then you can simply write a JQL type=bug and status = "Fail Testing" In the status field you can write the name of the exact status.

Is the admin account part of the "Service Desk Team" project role which might be the reason the account is counted towards the agent license. From the docs Global permissions At installation time, JIRA Service Desk creates a global permission named JIRA Service Desk agent access. If agent based pricing is enabled for the…

Scripted Custom fields is something which you can use. I use them quite a lot for displaying values which are calculated based on the issue data. This feature is part of the script runner plugin. It's a paid plugin and comes with tons of features. More details here…

In the post-function of the workflow transition (TO do > "Not Doing") it's generally a "Generic event" which is triggered. "Issue Update" events are triggered when you change value of a field on the issue, thus triggering issue update event. For workflow transition you can add post-function to trigger "Issue update" event…

Your welcome. Could you please accept/up-vote the answer so that other's are helped.

Hi @NT has the issue been resolved? If yes, please accept/upvote the answer. thanks.

Out of the box you can't perform this kind of aggregation on the JQL search results. To implement what you want, and if you have the script runner plugin installed. Then you can easily do it by creating a scripted field and using that scripted field to display number of bugs linked to the story. And then display this…

It's not possible to change start date of closed sprint through the UI. Though you can make the change directly in DB, but making direct Db changes is something which is discouraged unless you have a strong business case. Please read here…

Code sample (performing JQL in scripted field) -https://stackoverflow.com/questions/31978345/groovy-scripted-field-to-display-result-of-jira-jql

Just perform a JQL search within the scripted field. You can easliy create the proper jql since you have the issue object. From issue object you can fetch the project key and thus create a JQL string like def projectKey = issue.projectObject.key String jql = <below value> project = $projectKey and type = "project info" And…

So has your issue been resolved?

You just need to have a scripted custom field and in it's context, map it to all the projects and then add the field to the "view screen" of all the issuetypes in the project's screen configuration scheme. Thus, everytime the issue loads the script on the scripted field will be executed and in the script you will be…

Control chart is something you can use. About the Control Chart The Control Chart shows the Cycle Time (or Lead Time) for your product, version, or sprint. It takes the time spent by each issue in a particular status (or statuses), and maps it over a specified period of time. The average, rolling average, and standard…

https://confluence.atlassian.com/adminjiracloud/adding-editing-and-deleting-an-issue-type-844500747.html 

Hello @Jennifer Palsgrove You can create the Initiative issueType your self from the issueTYpe admin section. You dont' need to buy portfolio for using the Initiative issueTYpe. You can create this type yourself and start using it even without having portfolio. Portfolio documentation uses this type just for example sake,…

Yes you can do that, in the scripted field you can fetch the custom field value from the issue of type "project info" and then return that value as a string. You can fetch the value either by hard-coding the issue key or using an JQL in the scripted field.

https://scriptrunner.adaptavist.com/latest/jira/listeners.html#_custom_listeners 

The link which is shared with you is the example from script runner only.

In the validation phase of the workflow transition you can use the issueLinkManager.getOutwardLinks https://docs.atlassian.com/software/jira/docs/api/7.6.1/com/atlassian/jira/issue/link/IssueLinkManager.html#getOutwardLinks-java.lang.Long- This will give you all the links, you can traverse over the links using .each {}…

You need to write a custom listener, which will be triggered everytime there is a change in the custom field value of the project info type and then traverse over all the issues of the project and update them with the value coming from project info issueType. An example here…

Please see this article - https://confluence.atlassian.com/jira/setting-a-default-value-in-the-description-field-166003857.html If you have script runner plugin installed then this is how it's done. https://scriptrunner.adaptavist.com/latest/jira/behaviours-overview.html

Please accept the answer/upvote if your satisfied with the solution.

I am very surprised by this requirement of yours "On one of the sub-task issuetype work-flow when sub-task is resolved, it will create 5 more sub-task. ". Why is resolving an sub-task creating more subtasks? What's the Business case behind it. Using plugins which you have mentioned you can achieve the original requirement…

Hello @[deleted] Why are you using SQL, JIRA db is pretty complex and this would require coming up with a pretty heavy nested SQL (if at all it's possible). Have you tried Tempo timesheets, you can use lot of filters and in combination of the users/account/boards/projects and thus get the reports you want.…

Using the native project import tool will overwrite all the existing project data of the project already existing in the target instance. You can't cherry pick issues which you want to import. Whole project get's imported. If you still want to import only 50 issues then you can go for CSV import and import only the issues…

Please see the docs here -https://confluence.atlassian.com/jirakb/mapping-a-screen-to-a-workflow-transition-720634253.html