Fazila Ashraf Community Champion

hmm.. what else do you see in the history before the parent became none? Also what do you see in the child issue's history?

Hi @視恵 手塚 Welcome to community! Sorry to here about this event :( Was there any change to the global issue hierarchy configurations? Or was this particular Epic was converted into a different type and back? Or it could be possibly done by an automation? Did the parent field value also reflected the change?

Hi @max The group of subtasks are under the task. So you can call the parent task as "admin" for the use case?

Hi @Tim Geraghty Welcome to community! Recommend you to directly share the feedback to Atlassian team via https://support.atlassian.com/contact/#/ 

Hi @julia casagrande So in the Default assignee of the component, you do not see 'Component lead'? Or are you checking in the project details' default assignee? Does this component lead has product license and assignable issue permission?

Found the atlassian content that talks about this -> https://confluence.atlassian.com/jirakb/internal-users-showing-duplicate-on-user-picker-fields-1026039853.html For the current duplicates, you could use the migrate users functionality. But that is not a solution to prevent such future duplicates. I believe the option…

Open the epic and try changing the color like below Откройте эпопею и попробуйте изменить цвет, как показано ниже.

I agree :) Please request Atlassian for this in https://jira.atlassian.com/browse/JSWCLOUD-26729?jql=project%3DJSWCLOUD%20AND%20type%3DSuggestion%20AND%20statusCategory!%3DDone%20ORDER%20BY%20updated But looking at their Development backlogs , i do not think they can deliver the request anytime soon 

That field is a special field used to record the epic's colour and cannot be used as a normal custom field Это специальное поле используется для записи цвета эпопеи и не может быть использовано как обычное пользовательское поле.

Hi @Trần Tài Feature not available in JSM but found a commercial app in the marketplace that can help with this -> https://marketplace.atlassian.com/apps/1222472/requests-export-for-jira-service-management?tab=overview&hosting=cloud 

Hi @Margaret Lokonon Amodhing Welcome to community! Can you explain more on how the email is linked and shared? Only the issue's customers who are request participants or reporter gets email alerted usually. Do you have an automation or some other configuration that add a particular customer account as request participant? 

Hi @Alfabes Are you on a free plan or standard plan? Referring to https://support.atlassian.com/cloud-automation/docs/automation-service-limits/ , send email action -> 100 emails in a 24 hour period. This limit only applies to the Free edition of Jira Cloud and Trial licenses.

Hey @Mindaugas Ambroza There is no ticket as community is not same as Atlassian support :) I am an atlassian expert voluntarily contributing for the questions of other community users ;) If my answer had helped, you can choose to click on 'Accept answer' to close the thread and help others easily get the solution 

What you can do is, like how you have if issuetype = subtask, you can also validate whether reporter = given user sample, 

Hi @TL FINS Welcome to community! Could you explain your question in detail? What do you want to not duplicate?

Hi @Mindaugas Ambroza Welcome to community! If i understand correctly, you can use the condition block to validate if the reporter as specific person and then set the specific assignee

Hi @Chandan Kokane Work with your site admin as those instructions are specific to your org and i dont have access to it. Please share the hint that you are looking to use groups (either Atlassian group or IAM connected group what ever is available in your site) and they should able to guide you further.

Hi @Chandan Kokane Welcome to Community! Is your site using Atlassian groups or connects to any IAM groups? If so, you can use those groups. If they are not connected , then the distribution list will be just considered by confluence as yet another email id.

Hi @韦哲 Welcome to community! Are there other org admins for your site? If yes, you can ask them to set a new one. If not , please reach out to atlassian support https://support.atlassian.com/contact/ 

hmm not built in but you can explore third party apps for this feature. An example app is https://marketplace.atlassian.com/apps/1211591/versions-hierarchy?hosting=cloud&tab=overview 

Hi @Sushmita Chakraborty Recommend you to look at https://support.atlassian.com/jira-service-management-cloud/docs/connect-microsoft-teams-to-your-service-project/ 

Hi @Mohammed Siyad If you are looking to only migrate data, have you looked at the CSV importer already?

@Dawn Criswell , if you want to automate with this label logic, you can make an automation like below

Hi @Olivier B_ hmm interesting.. May be there is a workflow property on the initial status and it is conditionally restricting comment only for this issue type?

Hi @Brian Dulin What do you refer as Enterprise Jira/Confluence? Do you mean jira cloud enterprise plan or data center? What kind of connection are you expecting between the sites?

Hi @Vijay Dadi If the project is not going to use it, does it make sense to remove it from the project configuration altogether? If you want to retain existing issues with the same type, you could archive them if you are on premium or may be they could be moved to a different project?

https://confluence.atlassian.com/jirakb/how-to-find-any-custom-field-s-ids-744522503.html has multiple approaches. Your site admin can easily look at the list of custom fields and find the ID To identify your sprint id, refer…

It has to be done via the advanced options. In my jira site the sprint (locked field) is of id 10007. So the automation block below works for us where 10874 is the sprint id for a particular sprint

Hi @Ly Lim So "Pre planning" is a sprint in Jira terms? Yes, You can create automations blocks to update the sprint value for issues matching your conditions.

If there is a way to identify the existing second subtask in the automation configuration (may be the subtask 2 is a specific issue type), then this would work. The approach i originally suggested was to create the subtask 2 with the necessary fields as per your process when the subtask 1 gets resolved. and so on..