Tarun Sapra Community Champion

Hello @Mukesh Singh In your workflow the issue can go to bocked, but there are no transitions coming out from Blocked status to other statuses hence please add them. 

Hello @Mukesh Singh For scrum baords, Jira considers an issue "done" when it moves to the "right-most" column of the board, in your case that seems to be done. So the issues which are done should not appear in the backlog or your next sprint backlog. Can you please share screenshot of your column configuration and the…

Hello @Kasturee it's not a bug on server rather a feature request. Here's the open ticket about it, feel free to vote on it. And if any answer helped you then please accept/upvote so that others are also helped. Thanks. https://jira.atlassian.com/browse/JRASERVER-60945 Show Issue Type Name instead of Icon in Issue Navigator

Hello @Quality Assurance Traffic Sprint assignment should always be done via the backlog view of the board by dragging and dropping issue on the desired sprint. If users start manually updating sprint values then if in case they map the issue to a wrong sprint then it can create lot of problems in the reports.

Hello @Ivo Rodrigues Lot of reports in Jira can be extracted from the issue navigator view (search page) of Jira. But currently it's an open request to have the attachment available in issue navigator view https://jira.atlassian.com/browse/JRASERVER-4737 You can create scripted field if you have paid plugin like Script…

Hello @Kasturee You are on server or cloud? Because on Cloud I notice that column display the text and icon both for Project type. But on server (7.13) I can see only the icon and not the name of the project type in the project type column

Hello @Magnus Approval flow is supported out of the box in JSD https://support.atlassian.com/jira-service-desk-cloud/docs/set-up-an-approval-stage-for-a-request/ https://confluence.atlassian.com/adminjiraserver/configuring-jira-service-desk-approvals-938847527.html

Hello @Phil Currently it's not possible to configure the filter for complete/done issues for next-gen project. It's an open ticket - https://jira.atlassian.com/browse/JSWCLOUD-17257

Hello @Monika Jaisingh If you are satisfied with the answer, please accept/upvote so that others are also helped.

Hello @Emanuel Konringer Can you please share more details about what kind of event if being triggered. And what kind of form you are submitting and exactly when do you want the event to be triggered?

Hello @Monika Jaisingh Currently it's not possible to configure the next-gen boards and thus you have this default feature wherein the resolved issues are archived after 14 days. Here's an open ticket about this https://jira.atlassian.com/browse/JSWCLOUD-17257

"And those should be required. I allready have a transition screen but when i make the fields required they are reuqired for every creen of this issue type" To make the fields required on the transition screen you will need a paid plugin like JSU See here…

Hello @Sebastian Gastager You can have required fields on issueTypes, when you talk of "status" do you mean having required fields when changing status? And if that's the case then it's easy to implement such a thing. Just add a transition screen for the transition when changing status and make fields mandatory using a…

Hello @Bill Sheboy Indeed, it's no longer free it seems.

This one https://jqlsearchextensions.atlassian.net/wiki/spaces/SEARCH/pages/30497099/JQL+Reference+Server#JQLReference(Server)-AllIssuesInEpic(jql-queryorissuekey)

Hello @Aviad S Using the built-in "Epic Link" reference in JQL you will only see the list of stories but not their linked tasks or their child sub-tasks For that you will need plugins like JQL extensions (free plugin) or Script runner (paid plugin)…

The even was introduced in 7.5 i think, hence one JIra instance can be an earlier version of Jira. The even object in the listener should return to you the issueLink and using issueLink you can get source and destination object both.

Hello @Markus Rösner As per the REST API you get only basic system fields of the linkedIssue hence the only way it seems possible is to iterate over the list of linkedIssue and do a REST call for each one of them and in that rest call just fetch the desired custom field value of the LinkedIssue.

And here's the API for the event, from the event object you can get issueLink and from issueLink you can get sourceObject and destinationObject thus you will get objects of both issues involved. https://docs.atlassian.com/software/jira/docs/api/7.6.1/com/atlassian/jira/event/issue/link/IssueLinkDeletedEvent.html

Hello @SWAPNIL SRIVASTAV You can write a custom listener with script runner plugin which should listen to the event "IssueLinkDeleted" and in the listener you can update the custom field value for the issue as null.

Hello @Alexey Matveev Since Epic-link is a locked field thus it's not possible to have it mandatory in the field configuration as I always make it required in the workflow validation of the transition.

Hello @Gabor Laksamada It seems you have set the epic-link field as required in the workflow validation phase of the create transition. And you are using the same workflow for sub-tasks as well and thus unable to create them. Please use a different workflow for sub-tasks in which the epic-link field is not mandatory in the…

Hello @Oleksandr Lozinskyi You can achieve this using control chart in the Kanban board and that has the option of "quick filter" wherein you can filter the incoming issues based on the T-shirt size. https://confluence.atlassian.com/jirasoftwarecloud/control-chart-777002660.html

Hello @Thyagaraj Gopalakrishna Out of the box it's not possible, if oyu have a paid plugin like script runner then you can follow this example and implement what you want. http://scriptrunner-docs.connect.adaptavist.com/jiracloud/post-functions.html#_calculated_custom_field

Hello @Operations_Support What you require is currently an open ticket in Jira https://jira.atlassian.com/browse/JSWCLOUD-17442 Option to Drill Down in Next-Gen Roadmap

I have found an open ticket, something similar to what you require for your users, but it's an open ticket and still unresolved. https://jira.atlassian.com/browse/JRASERVER-64204

Hello @Aleksandra Kalischek Currently it's not possible to have the plus icon if there are no existing sub-tasks for the issue. I am not exactly aware of the customization in the Jira code which might need to be done for this feature to be available.

Hello @Aleksandar Balicevac Your request is currently an open ticket in Jira. https://jira.atlassian.com/browse/JSWCLOUD-17740 As a Jira Software user I would like to add any Issue types to the next-gen Roadmap

Hello @Владислав Яшин Scripted fields, when they depend on data from outside then the index is not updated unless the issue on which the scripted field is present is modified. This is one of the short-coming of the script field and also explained in the docs From the docs It’s worth expanding a little on what I said above.…

Something like this https://community.atlassian.com/t5/Adaptavist-questions/Get-sla-value/qaq-p/685749