Tarun Sapra Community Champion

Hello @Ian Phillips Epic link field is currently not fully supported in the next-gen projects. Please see open tickets https://jira.atlassian.com/browse/JSWCLOUD-17231 https://jira.atlassian.com/browse/JSWCLOUD-17389 https://jira.atlassian.com/browse/JSWCLOUD-16990

Hello @Prudvi Kumar Penmetsa By tasks you mean "Task" type or "sub-tasks" because sub-tasks aren't included in the Burndown chart. As per the docs The Burndown Chart is board-specific – that is, it will only include issues that match your board's saved filter So if the board filter includes Tasks and you have estimated…

Hello @Nitesh Nilajgi Currently, it's not possible to copy a space in confluence, please see the KB article https://confluence.atlassian.com/confkb/how-to-copy-or-rename-a-space-in-confluence-169578.html You would need to use paid plugins for this purpose as it's not supported out of the box.

Hello @Madhva This is not possible without some script or user actually changing the issueType. Can you please see the issue "activity" or issue "history" and share the screenshot of that so it becomes clear as to how the story is converted into bugs

The Kanban board is just a view on the tickets being fetched by underlying filter. If you make changes in filter then you can remove the tickets from appearing. Another way to do it is to avoid making any change in main filter but rather add a sub-filer in the Kanban board configuration.…

https://confluence.atlassian.com/adminjiracloud/customizing-jira-service-desk-permissions-776636379.html

Hello @Maria Bonello In order to transition issues, please see the permission scheme of the project. https://confluence.atlassian.com/jirakb/standard-permissions-in-jira-service-desk-838416600.html (Generally it's only the agents actually working on the tickets which can do this change) Transition Issues Service Desk…

Hello @s.p.mallu poojari There is no separate permission for create branch as it's part of development panel https://confluence.atlassian.com/jirasoftwareserver0711/viewing-the-development-information-for-an-issue-955166300.html Currently there is no way to hide the "create branch" , please see this open ticket…

Hello @s.p.mallu poojari For rest of the projects just disable the "development panel" from the project permission scheme View development tools (only available to JIRA Software users) Permission to view the Development panel, which provides you with just enough information to evaluate the status of an issue's development,…

Congratulations to all winners!!!! 2018 was definitely an awesome year. Getting to meet fellow champions in Barcelona at summit. It was my first summit and had the opportunity to give a talk as well at the Summit. Amazing memories! Looking forward to a rocking 2019 !

Description seems to be incomplete, I would suggest you to reach out to Atlassian support in this matter, so that they take note of it and update the description.

Hello @Johan Abildskov The reason "Schedule Issue permission" is required is because when you add/remove issue into sprint then not only you change the Sprint field (edit permission) but you also change the Rank of the issue. And this is where "Schedule issue permission" comes into picture, under the hood it seems that…

https://confluence.atlassian.com/confcloud/restricted-functions-in-confluence-cloud-734070955.html

Hello @Diego It seems the user @Gilbert Louis is using Confluence cloud, thus I don't think "User macros" are possible on the confluence cloud.

Glad to know @Nafisa_Latif that the problem has been identified. 

Hello @Nafisa_Latif Is it happening in all browsers, or it could be that the browser doesn't have sufficient memory due to being executed on a virtual machine.

Hello @Jamie Harrop Here it is project = [PROJECT] AND status changed to ("Published", "Live") AFTER startOfDay()

Hello @Ori Katz Bulk cloning is not supprted out of the box in Jira https://jira.atlassian.com/browse/JRASERVER-37520 Similar questions (you need to install some plugins for it) https://community.atlassian.com/t5/Jira-questions/Bulk-copy-clone-issues-from-one-project-to-another/qaq-p/89770…

Hello @Ori Katz Regarding your requirement import all the tasks from another project You can just use Bulk move operation to move issues from one project into another project.…

Hello @Stephen Connolly Your requirement is an open ticket right now, let's hope that it gets implemented soon by Atlassian. "As an admin, I'd like to place custom fields between the description and the comment section in the New Jira issue detail view" https://jira.atlassian.com/browse/JRACLOUD-71075 List of all tickets…

Another helpful read https://confluence.atlassian.com/jirasoftwarecloud/configuring-estimation-and-tracking-764478030.html#Configuringestimationandtracking-moreMoreinformationaboutestimationandtimetracking

Hello @mirelm Your requirement has been discussed many times before on this fourm, please see the following threads https://community.atlassian.com/t5/Jira-Software-questions/Story-points-subtasks-gt-burndown-chart/qaq-p/178924…

https://marketplace.atlassian.com/apps/5048/jsu-suite-utilities-for-jira?hosting=server&tab=overview https://marketplace.atlassian.com/apps/1215067/wtf-workflow-tools-and-functions?hosting=server&tab=overview https://marketplace.atlassian.com/apps/292/jira-misc-workflow-extensions?hosting=server&tab=overview

Hello @Arindam Bhattacharjee You would need to use a plugin like Jira Suite utilties or other related paid plugin to add a field validator on the transition. In the field validator transition you can choose the field "timespent" and make it mandaotry for the transition. But also, make sure you have added the time tracking…

Hello @Ollie Guan The Kanban boards do support a "Backlog" view in Jira. We don't need to use scrum board for backlog view as Ops teams that generally use Kanban mode can use the backlog view. I have shared the links in my answer for the JIra server.

Hello @Cindy Tan Please see the following links to the docs, which explain as to how to "enable" the Kanban backlog and how to then start using it. Use Kanban backlog https://confluence.atlassian.com/jirasoftwareserver0710/using-your-kanban-backlog-953146528.html Enable Kanban backlog…

Or use the change keyword status changed TO closed AFTER startOfDay(-14) 

Hello @Zara This will give you the issues which have been "Closed" in last 14 days. status was not Closed BEFORE startOfDay(-14d) and status = Closed

Hello @Dean Stearn Great to know that it worked, please accept/upvote the answer so that others are also helped. thanks.