Manoj Kumar Gangwar Community Champion

You can follow the below doc for this. https://support.atlassian.com/user-management/docs/delete-a-managed-account/

Hi @Marcia Booth, It is a Bug in Jira. https://jira.atlassian.com/browse/JRACLOUD-85520 As a workaround, you can refresh the page and then it will back to the basic mode again. 

Hi @まぷれゆ アカウントを削除するには: id.atlassian.com/manage-profile でアカウント設定にアクセスします。 「アカウント設定」を選択します。 「アカウントの削除」セクションに移動し、「アカウントの削除」を選択します。 アカウントを削除する前に、削除されたアカウントがどうなるかをよくお読みください。 [アカウントの削除] を選択し、表示される確認ダイアログで削除することを確認します。 KB: https://support.atlassian.com/atlassian-account/docs/delete-your-atlassian-account/

Hi @srodionov Welcome to the community! Please check the below thread replied to by the Atlassian Team. https://community.atlassian.com/t5/Confluence-questions/Delete-organisation/qaq-p/1685818

Hi @Mina Kim2 Welcome to the Community! Please try another browser and then check. If the issue persists then check the permission with your space admins.

Hi @KOBAYASHI HIROKAZU _JALDX HPI_ You need to grant the create issue permission for the automation for Jira user by adding the "atlassian-addons-project-access" user in your permission scheme.

You can try incognito window mode in the edge browser. 

Hi @Tristan Fowler Welcome to the Community! You can update the emoji in the Slack workflow configuration and change the emoji under the event.

Yes, It should be sufficient. You can try the webhook option to link it.

Hi @Benoît Voisin Can you try direct URL and check? XXXX.atlassian.net/secure/admin/CloudImport!start.jspa

Hi @Benoît Voisin Welcome to the community! To import your backup file: * Choose Settings () > System * Under IMPORT AND EXPORT, select Import Jira Cloud and follow the steps.

Hi @Ryan Manahan Welcome to the community! Have you tried a different browser if not please try and check.

Hi @Osama Khalaf Welcome to the community! Please wait for some time and then check again. If the problem persists after maintained window then reach out to the support team via raising a ticket. https://support.atlassian.com/contact/

Hi @Maria ZIOGA Welcome to the community! It happens if you create tickets in bulk and then delete all of them. It is not feasible to go back and start from 1. The only way to reset the keys is to delete the project. The real question should be: Why do you want to reset the numbering? Is it just for aesthetics?

You should have atleast a Standard Plan.

Hi @Logan, Lakshmi Welcome to the community! Could you please share the screenshot? Also, try changing Zoom in the browser and checking if it shows up.

Hi @Mohit Edupuganti You can remove all groups from the space permissions and add the developer group only if no group adds them as individual users. Also, use the parent-level page restrictions and grant view/edit permission only to developers.

If you have admin permission then you can use the below URL to get the field name. https://<your_jira_site>/secure/admin/ConfigureCustomField!default.jspa?customFieldId=10254

Please go to the custom fields and edit any field then replace the field id with 10254 in the URL and search. Then you can find the field name which is causing issue.

I don't think, we can change the form based on the field selection.

Hi @Ben Øye You can check the marketplace apps for auto log work. I found the below app, you can search for similar apps. https://marketplace.atlassian.com/apps/1211125/automated-log-work-for-jira

Hi @jlm Welcome to the community! Please try in a different browser and check if the issue persists then you can raise a ticket with the Atlassian vendor using the below link- https://support.atlassian.com/contact/

Hi @Kratika Shastri Welcome to the community! I have only seen this happen when a story/task level issue has been closed while sub-tasks of that (closed) issue are still unsolved. That is indeed a scenario you would want to avoid. In company-managed projects, you could use a subtasks blocking condition in your parent…

Do you have the "Issue Priority" field on the issue creation screen? If not, check the Issue Fields and if the field is required from there then make it non-mandatory.

Hi @Nagesh Shastri Welcome to the community! Please check the mandatory fields at the time of issue creation and same fields should be added. 

Hi @Micha van Tol Welcome to the community! I don't think we can fix it but we can only adjust it.

The number of fields a user can pin depends on the length of the custom field IDs they pin. For example, one user might be able to pin 7 fields, while another user might be able to pin 11 fields.

Hi @angela_williams Welcome to the community! The number of fields you can pin in Jira is limited by the amount of space each field's ID stores. This limit is 255 characters. Here are the suggestions for the same. https://jira.atlassian.com/browse/JRACLOUD-78946

Hi @Amélia Sehrine Welcome to the community! I thought everyone was receiving the recap so you should also receive it. you can wait for a few days. 

Hi @Semanur Uyar Welcome to the community! If there was an update or configuration change that modified the overall theme or style settings of your calendar, it could have impacted how colors are displayed. The legend may now default to a gray scheme, overriding the original color settings.