Manoj Kumar Gangwar Community Champion

Hi @Sreenivasulu , I don't think it is possible to hide that option. 

Hi @Angela Wagner Welcome to the Atlassian Community Make sure that the time tracking field is added on your edit and view screens: Go to project > project settings > Issues > Screens Select the screens of your issue types to which you want to add the time tracking to, and add it Cross check that now is visible.

Then last it could be due to fields have default field value option set. 

If the fields are not available on any of the screen then these fields are updating via automation rule or workflow post function. Could you please check the ticket history and check if both fields are showing in history? 

Okay, I was giving the suggestion based on cloud. If you on DC then you need to go the project settings>Screens>search for the POC - Service request screen scheme under that there should be 2 screens check the edit screen and remove these fields. 

There should be one more option (Issue View) next to fields but it is not there. You may raise a request with atlassian vendor to fix this issue on your instance. 

At the right side you will see an option to search the fields and add these fields then move it under hidden fields. 

As per the 1st screenshot, click on the edit fields option then you will see an option for Issue View over there you can check these fields

Hi @Lan Anh , You can hide the SLA field from the view screen. Go to the Project Setting> Request Types>Search for the particular request type and click on it. After that Click on the Issue View option search for the Priority & Label fields and move it under Hide when empty section.

Hi @Lan Anh , You can hide the SLA field from the view screen. Go to the Project Setting> Request Types>Search for the particular request type and click on it. After that Click on the Issue View option search for SLA remove it

Hi @Martina Bassi Please refer to the below document. https://confluence.atlassian.com/jirakb/how-to-add-group-members-as-request-participants-1388151755.html

Hi @Josh Noren You can use the Search screen to filter for the issues you want to close. Then use the Bulk Change feature, and select Transition as the action. Step 4: uncheck the box for Send mail for this update The bulk change for transition can be affected by the starting status of the issue and by workflow rules, so…

Hi @David Smith , Welcome to the Atlassian Community! Sub-tasks are of little use in a backlog, they're not rank-able outside their parent issue, and are not sprint items themselves, so there's not a lot of point in seeing them. You can get a view of them in a backlog by adding the "sub tasks" field to the backlog view of…

You can add a branch and then copy form from parent or trigger issue

You can change copy from to parent then test

Hi @Harish Sharma , Welcome to the Atlassian Community! You can create an automation rule similar like below-

Hi @Sascha R_ Start in the incognito mode and try again. If this doesn't work , something is wrong from the Atlassian backend. You can raise a support ticket for them here: https://support.atlassian.com/contact/

Hi @Kateryna Shapovalova , It seems like an issue with the Atlassian end.

If our responses were helpful please consider clicking on the Accept Answer buttons to mark your Question as Solved.

Hi @Max Nazarenko , Welcome to the Atlassian Community! You need to edit the Field Configuration for that issue type and check the required field. 

Hi @Ryan DePalma , Welcome to the Atlassian community!! Check the workflow validator on issue creation if there is any field set as required which is added to the create issue screen. The error appears because some fields are mandatory on issue creation.

https://support.atlassian.com/jira-cloud-android/docs/manage-your-notifications/

Hi @Aleksandr Chushev Welcome to the Atlassian Community! Please check with your admins if the push notification is enabled for mobile. https://confluence.atlassian.com/jirakb/how-to-enable-jira-push-notifications-on-jira-mobile-app-android-ios-1369276456.html

Hi @Myles Boyd , As per my knowledge, It is not feasible with Jira native functionality but you can achieve this using the plugins. Or you can use some workaround. https://confluence.atlassian.com/jirakb/automatically-reassign-issues-of-agents-who-are-on-vacation-with-user-properties-1277100927.html

Hi @Samrudhi Shete , You can create an automation similar like below:

Hi @Cindy Phillips , Welcome to the atlassian community! Could you please share the error screenshot? 

@Ravi Prasad If our responses were helpful please consider clicking on the Accept Answer buttons to mark your Question as Solved.

@arkadi kaplon If our responses were helpful please consider clicking on the Accept Answer buttons to mark your Question as Solved.

@Melanie Calothi If our responses were helpful please consider clicking on the Accept Answer buttons to mark your Question as Solved.

@jože If our responses were helpful please consider clicking on the Accept Answer buttons to mark your Question as Solved.