Tarun Sapra Community Champion

Hello @Joeri Bruneel For the backlog, the task is done if the status of the task is same as the status in the "right most" column of the board. Are you using Kanban or scrum? If you are using Kanban you you can choose to see only recently done issues.

Hello @Surender Reddy If the answer helped you, please accept/upvote so that others are helped as well.

Hello @ingmar morssinkhof Out of the box it's not possible to clone to another issue. What you require is also here - https://jira.atlassian.com/browse/JRASERVER-8016 It has been marked as won't do by Atlassian.

Hello @eperi When you say - "And it should not be automatically created." What do you mean, please elaborate as to how you wish the remote issue to be created as both instances are not the same thus the issue should be created in a remote JSW instance. 

Hello @eperi Yes, you can create a Linked JSW ticket. Please see the KB article from Atlassian here https://confluence.atlassian.com/servicedeskcloud/blog/2017/12/automatically-create-linked-issues-from-new-requests

Hello @Manus Tangtirawat Here is a possible duplicate question https://community.atlassian.com/t5/Marketplace-Apps-questions/Custom-Fields-on-a-Linked-Issue-is-updated-based-on-field-value/qaq-p/646406 There are built-in automation rules available for JSD…

Hello @Surender Reddy Here's how I will do it using Script runner plugin. For each sub-task to be created you can use the post-function of the plugin called "Create a sub-task". Now in the post-function configuration there is an option to add "condition". In that condition you can check if the corresponding checkbox has…

Hello @Ankita Sinha It's "Manage subscriptions" in the billing section.

Hello @Surender Reddy For Quick-sub-tasks plugin I don't see the option of add a condition, if you were using other paid plugins like JSU or Script Runner, then it would have been straightforward. 

Hello @Jennifer Hemmens The documentation links available on the JSD ticket can easily be restricted to only dev teams and agents. Thus, the dev teams can easily access them via the linked JSD ticket. 

Hello @Surender Reddy You can create a custom field containing checkboxes. Each checkbox should correspond to each sub-task. Then add the custom field on the issue create screen and based on the selection of the check-boxes you can trigger corresponding sub-task creation. You must be using a plugin for sub-task creation…

Hello @Jennifer Hemmens In this screenshot, Jira has automatically picked up the pages (based on content) from the knowledge base article. But exact underlying algorithm, if it's component based or label based etc can may be shared in more detail by someone from Atlassian. But the page links are automatically displayed…

Hello a page from the knowledge base article can be displayed in the issue view screen if the content of the tickets matches that of the page. See below in the screenshot "Related knowledge base articles"

Hello @Jennifer Hemmens The links to the documentation are not automatically included, but the customer can quickly do a search But the linked documentation can appear automatically as the customer types in the request in the JSD, see pic below from docs. Also yo ucan customize the permissions for JSD and the docs as to…

Hello @Jennifer Hemmens Atlassian already provides a similar feature as to what you require. Basically you can link your Service desk with Confluence knowledge base So that Customers and Engineers don't spend time on repetitive tasks and solutions.…

Hello @Mahendar Daripalli If you want to populate custom field values directly from DB then you would need to use a paid plugin like nFeed. https://marketplace.atlassian.com/apps/23337/nfeed-external-data-in-custom-fields?hosting=server&tab=overview

Hello @nishanth.shenoy You will need to use a paid plugin for implementing this feature. Something like nFeed or Script Runner. Code sample for similar scenario for Script runner plugin https://scriptrunner.adaptavist.com/latest/jira/behaviours-conversions.html#_walkthrough_external_rest_service

Hello @Tiedemann Marc If I select this option "Show Open" for the sub-tasks of the user-story then this option is persisted if I open other stories in the "old issue view". But in the project level, I don't see an option to persist this across the project or at a global level.

Hello @Tiedemann Marc Currently it's not possible, please see the open ticket here https://jira.atlassian.com/browse/JRACLOUD-71447

Hello @Fiaz Glad to know that now it's working, please accept / upvote answer so that others are also helped.

You can get the project lead user name and then update the issue with issueManager def userName = issue.getProjectObject().getLeadUserName() The use the code sample from below to update/edit an existing issue https://developer.atlassian.com/server/jira/platform/performing-issue-operations/

Hello @Māris Freimanis Add a custom listener which is listening to issue move events and in that listener you can write the code to update the assignee.

Hello @Svenja Speen This is a unanswered duplicate question https://community.atlassian.com/t5/Answers-Developer-Questions/Return-length-of-time-an-issue-has-been-flagged-for/qaq-p/466753 It's not trivial to calculate the time till resolved on a issue which was once a impediment (flag) My suggestion to you is to move the…

Hello @alan rossney You have to make sure that "Priority" field is part of the "Edit screen" configuration of the story issueType. 

Hello @Fiaz Which "template" do you want to switch? In the next-gen projects you have "feature" settings in the project setting which you can use to toggle various features like roadmap, Sprints, backlog etc

Hello @Mark What do you mean by "moving an issue from one board to another"?

If my answer helped you, please accept/upvote so that others are helped as well.

Hello @Imran ahmed If you have project admin rights then you can add new versions to the project https://confluence.atlassian.com/adminjiraserver0712/managing-versions-959313592.html

In the "global permissions" there is a permission called "Create next-gen projects", just make sure that only admins have this permission so that normal users can't create next-gen projects.

Hello @Alan Levin Currently, there is no way to convert next-gen to classic projects. You will have to bulk move issues from next-gen to classic projects. Yes, you can disable the option for others to create next-gen projects.