Tarun Sapra Community Champion

Hello @עדי וקנין Is the status closed mapped to the "right most" column of your Scrum board. Because JIRA boards consider an issue as done only when the issue is in the right-most column of the board. Because if they are not in the right-most column then when you close the sprint then those issues will move to next sprint.

Hello @[deleted] Please read the complete documentation here https://confluence.atlassian.com/confeval/jira-service-desk-evaluator-resources/jira-service-desk-how-jira-service-desk-works-with-jira-core-software From the above link Jira Service Desk issues can easily be moved into Jira Software projects for development,…

Hello @Hannah Tattersall The idea of moving issues from one board to another is actually incorrect because boards in themselves are nothing but a view on the issues. The boards show issues based on JQL filters. So if your board A is showing issues based on JQL filter A and you want board B to show the same issues then in…

Hello @Andrew L Is Duplicate an bi-directional link? Because I think it's working fine because for the innerLink on the sub-task you see the dedfault "jira_subtask_link" which exists between the existing sub-task and its parent and the "duplicate" link which you have set can be a uni-directional outer link from the…

Hello @Raju Anumula Project admins can add the fields in screens in their JIRA projects from 7.4 onwards but under these conditions * The screen must not be a default system screen. * The screen must not be shared with any other projects, or used as a transition screen in workflows. * The project admin can add, remove and…

Hello @Robert Lack If it works for you then could you please accept/upvote the answer as that will help other users as well.

Happy to help, if it works for you, please accept/upvote the answer.

There are plenty of examples available on this forum if you just search for them. https://community.atlassian.com/t5/Jira-Core-questions/Behaviour-plugin-Show-Hide-customfield-in-Create-screen/qaq-p/58252…

Hello @sudheer You can have the hierarchy you want, using the "Issue linking" feature. From your hierarchy it seems that you are trying to implement the "SAFe" framework in JIRA which is fine as well but I personally recommend to stick to "Epic<->Story" hierarchy in JIRA because it's so tightly coupled in JIRA. So when you…

Script fields is for showing calculated data based on issue data and not for show/hide of fields. From your code sample it seems you are trying to hide a custom field based on the value of priority. For achieving this you have to use the "Behaviour module" of the SR plugin instead of script fields.…

You can create a separate "swim lane" on the board to show tickets which haven't been updated in last x days. So you can write a JQL in the swim lane like updatedDate < startOfMonth() Tickets which haven't been updated this month or you can also use a "quick filter" but it all depends on your definition of "out of date" or…

Hello @paul bryant I haven't used requirement yogi, so can't share much about it. But while implementing the requirements management process I generally use built-in confluence and jira capabilities along with 3 essential plugins for reporting purposes. As it's very important to have effective reporting dashboards for all…

@Alana Fernando - Your welcome! :)

Hello @paul bryant , Now, I clearly understand from your workflow what you are trying to implement. I have implemented something similar at my current place of work, thus I will suggest you not to go for 2 sprint loops but you are on the right track. Basically, for the Refinement process (done by BAs/POs) created a Kanban…

Labels are free ticket thus make sure you type the exact thing in the JQL as it is on the ticket. And other users also type the exact text. Since labels are free text thus I personally don't prefer to make use of them as chances of error are high because even a small typo would break the functionality. 

Hello @[deleted] Agility boards are only available on cloud version, are you using cloud version of jira or server version.

https://community.atlassian.com/t5/Jira-questions/How-do-I-add-more-fields-to-the-Service-Desk-Request-form/qaq-p/9005

More info here - https://confluence.atlassian.com/jirakb/list-of-supported-custom-fields-for-request-types-in-jira-service-desk-customer-portals-867182673.html

Possible Duplicate - Please see the below links

Hello @paul bryant You have asked a very broad question and frankly there is no concrete answer, because it depends on how your teams respond to the tools and there might be changes required in the process after getting few feedbacks from the team. Thus, if it's a large scale rollout of the Atlassian stack then it can take…

Glad to know that Sandra, if you are satisfied with the answer, then please accept/upvote so that others are helped as well.

Indeed, Script Runner documentation definitely has scope for improvement when it comes to beginner tutorials, may be have script console embedded into the site so that new users can play around the various features of the plugin without breaking much. I have been using the plugin for over 5 years now and here's how I…

Hello @Alana Fernando Above JQL would give inconsistent results because if an issue is closed in sprint 4 and now closed but was worked upon in sprint 3 as well thus in JQL if we use JQL "Sprint = Sprint 3" then we might get issues which were worked in sprint 4 and are now closed but were worked upon in sprint 3(as sprint…

Hello @Sriraman, As already shared by @Alana Fernando, it's not possible out of the box in JIRA to see the stories burned per sprint of an board/project in a single chart of JQL. Because in JQL you can use the query like "Sprint in (X,Y,Z))" to get the issues from all sprints, but categorizing per sprint is not possible,…

There can be various opinions as to how to do it. But I will follow the simpler approach. Basically have first two steps in the story workflow as refinement and then on the 3rd step onward it should be the backlog on the sprint board and the dev team which can work on the stories. Add a validation on the second step that…

Hello @DILEEP KUMAR The APIs are available here - https://docs.atlassian.com/software/jira/docs/api/7.6.1/ As i have already shared a code sample which was the original question, thus it has been answered. Please go through the APIs docs and the Script Runner docs

Working code import com.atlassian.jira.component.ComponentAccessor def issueService = ComponentAccessor.issueService def user = ComponentAccessor.jiraAuthenticationContext.loggedInUser; def validateAssignResult = issueService.validateAssign(user,issue.id, user.username) if(validateAssignResult.isValid()) {…

Hello @DILEEP KUMAR The code I showed is for updating the assignee but you also have to store the value in the DB, thus better use the issueService instead of issue.setAssignee method and then it should work for sure. Please see 2 code samples here…

And you can easily add a condition before the execution of the post-function, and if the condition is true only then the post-function will be executed.

If you have script runner plugin then it's a built-in post function to create a sub-task or to create an issue. You don't have to write a script for it.