Alex Koxaras -Relational- Community Champion

Hi @Pam Heishman This article will help you https://support.atlassian.com/jira-software-cloud/docs/customize-an-issues-fields-in-team-managed-projects/ for team managed (formerly know as next gen) projects.

Congratulation @Brant Schroeder ! Here's to another 400K kudos and to the next 10 (and many more) levels! Well deserved!

Hi @Craig Elliott and welcome to the community, It is possible to achieve that either by using a workflow postfunction, or using Jira Automation, or even by using a listener. The best choice depends on the existing solution of your projects. Best practice is to keep, if possible, all automation in one place, just so to…

There was an incident for yesterday https://confluence.status.atlassian.com/incidents/jwwx5y03pqdg which hopefully has been resolved by now. Can you please confirm that now it's ok? @Rahul @Casper Lumby @Kane McConnell @Harald Seyr @Scott Jablow 

You say you have: * Parent* Scope * Epics And I assume that inside Epics you have standard issue types and the latter have their subtasks. Your hierarchy would be: * Parent* Scope * Epics* Standard Issue types* Subtasks In jira from Epics you can create standard issue types by clicking "Create child issue type" (in cloud…

@Małgorzata Adamska-Piotrowska thank you for you reply. But how do you define their relationship/hierachy in Jira? 

Hi @Karin_Gleichauf Run a /rest/api/3/issue/ request on any issue that has a worklog: /rest/api/3/issue/KEY-XXX and search the response for that specific worklog. Under field "worklogs" you should search for that specific worklog ID: "worklog": { "startAt": 0, "maxResults": 20, "total": 1, "worklogs": [ { "self":…

Hi @Barry Guda and welcome to the community, This recreate issue is part of the Issue Templates for Jira app by Deviniti. In their documentation: https://deviniti.com/support/addon/cloud/issue-templates/latest/recreate-issue/ it states: If you recreate an issue A-1 from project A to project B, all children of A-1 and…

@Casper Lumby no I can't think of one. You should be able to raise a request.

Hi @Małgorzata Adamska-Piotrowska How are these epic "parents" are defined? Do they have a specific linking type?

Only paid plans are eligible to raise a request on support. Free plans get the help of community - where applicable.

Hi @Srikanth Vemuluri You can also use subscription filter (https://www.atlassian.com/blog/jira-software/jql-the-most-flexible-way-to-search-jira-3-of-4) using a JQL that satisfy your condition. You can then select a group of people to send emails for the results of the issues.

@Thomas Christof sorry for the late reply. I tried changing the remaining estimate and my rule triggers just fine.

@Neeraj Patil this is fairly easy to change in the existing rule. You have to tweak a couple of things:

@Neeraj Patil on standard issue types there is a checkbox under time spent/remaining estimate to include subtasks. This works for the two fore mentioned fields but not for the original estimate. What fields do you want to sum up?

@Rahul @Kane McConnell you should raise a request to Atlassian Support. This thing affect more that one instance and should be reported.

Hi @Ivan Andrieiev You can move it and thus turn it into a subtask. Or you can click on the top left corner of an issue (on view screen) which will edit the issue type and change it.

@Rahul then you should raise a request to Atlassian's support. Community can't really help you on this: https://support.atlassian.com/contact

Currently on https://confluence.status.atlassian.com/ there isn't a reported incident about any confluence systems. I just tried on my instance to export a pdf from a page and worked fine. Can you both of you try from a different browser, with private window and NO extensions loaded? In addition are you the only ones with…

Hi @Eden Eliyahu If you are talking about Jira automation and the creation of pages, then this is the page for you: https://support.atlassian.com/cloud-automation/docs/use-jira-automation-with-confluence/ * {{createdPages.title}} - returns the names of all pages created. * {{createdPages.url}} - returns the URLs of all…

Hi @Malte Redmann What kind of message are you getting? Are you on a free or paid plan?

Instead of doing a whole site export, you can always go with space-to-space migration. Meaning that you export individual spaces and import them. But Since Atlassian has already given us the opportunity to do that with one take, I would definitely take the zip file anytime. The other way is way too much time consuming.

@Saqib Dar kindly mark my answer as accepted in order to help others! Thanx!

Hi @Karl Stiller and welcome to the community, You can of course start with a free plan of <= 10 users, but this will have limitations. It doesn't matter if you will use the company email, since your company is not interested in using Atlassian Access etc. And of course the second option you are saying is also viable. You…

Ooh, my bad!! Apologies :) This is for confluence https://confluence.atlassian.com/cloudkb/migrating-from-confluence-cloud-to-confluence-cloud-691011969.html

Hi @Simon Hemming You can't do that currently in Jira. You can submit a suggestion for this matter here. In addition, you could do that with a workaround: * Create a new single select field with the customers statuses * Bulk change (or use automation rule to map) current internal statuses to "customer's statuses" * Create…

Hi @SaravanaKumar You can use the Migrate to cloud option from the admin settings. Read this documentation https://support.atlassian.com/migration/docs/perform-a-cloud-to-cloud-migration-for-jira/

Subtasks are a smaller pieces of work that needs to get done and usually we tend to break them down from tasks and they are less than a day's work. This help the developers chooses what to work on during their day.

Hi @Hansika Wijenayake You can't have two issue types with the same name in Jira, in the sense that you can't create two identical but different entities of work (e.g. I have a work that's need to be done called "Plant". You can't create a new work called "Plant", because you have already defined that piece of work!).…

Hi @Matheus Budi and welcome to the community, You should think about issue type hierarchy first and after that about grouping each issue type based on the "platform" or other type of grouping. For the latter you will use the build-in Components functionality, which do exactly what you want. So basically you can have the…