Gunjan Kumar Expert

Hi @Kelly Acheson Welcome to the Atlassian Community I’ve run into this as well. You can usually add screenshots when creating a new comment, but editing an existing one is a bit more sensitive. Jira tends to re-check the whole comment when you edit it, and if there are inline images or anything pasted in, it can fail with…

To use that, you just need to switch to the advanced search (JQL) view. In your issue search or queue, look for “Switch to JQL” (usually in the top right), then paste something like project = ProjectName AND status CHANGED DURING (-7d, now()). That will show only the tickets whose status changed in the last 7 days, and you…

Hi @Katie Lee I think the issue is coming from a role mismatch after the move to Service Spaces. Earlier, JSM used the role “Service Desk Customer”, but with Service Spaces Atlassian has shifted to a different customer model at the space level. The problem is that global configurations like the mail handler may still be…

Hi @Tyler Duggan the easiest way to handle this is to create a filter that only shows issues where the status changed in the last week (for example using status CHANGED DURING (-7d, now())). Then you can set up a weekly subscription for that filter, so your team only gets an email with tickets that actually had a status…

This is probably not a supported feature in JSM Cloud. If both fields showed together in your setup, it was most likely a one-off case or older behavior, not something that Cloud is meant to keep supporting. So even if it is still working in your current setup, I would not rely on it as standard behavior. The safer option…

Hi @Justin Goodemoot From what I understand, this is expected behavior in JSM. When an issue is cloned, the attachment may be copied to the new Jira issue, but that does not automatically make it visible in the customer portal. For portal visibility, the attachment needs to be shared in a public, customer-visible comment…

Hi @Marcel S Yes, this is expected behavior in JSM. If the Description field is linked inside a Form and you also try to add that same Description field directly to the request type, Jira will usually remove one of them or unlink it to avoid showing the same field twice. So unfortunately, this is not a hidden feature you…

Hi @Kenny Peere Welcome to the Atlassian Community In JSM, when someone clicks Decline from the approval email, Jira can reject the request straight away without opening the usual screen, so it will not ask them to enter a decline reason and any required field or validator on that step can be skipped.aaa Atlassian says…

Hi @Khira Niemeier Nothing is broken here, it’s just how Jira behaves now. The Issue color is mainly meant for Epics, so it still shows next to the summary there. For other issue types like Feature, the field can still exist, but Jira no longer displays the color in the header. This changed at some point, so if you still…

Hi @Pavankumar Machireddy Your understanding is right. In JSM, the email allowlist doesn’t actually control who can raise requests, it only affects how emails are handled. So if a user is already allowed through Customer Access, they can still create tickets via email even if their domain isn’t in the allowlist. To…

Your URL looks correct, and using PERIT3 as the project key is probably right based on the issue key PERIT3-2. The error you’re seeing is likely not the key, but because of authentication or permissions. In Jira Cloud, simply opening the API link in a browser usually doesn’t work. You need to use your email and an API…

Hi @Mohammed Abu-Rugaya Welcome to the Atlassian Community The problem is that PERIT3-2 is not a project key, but an issue key. In Jira, issue keys are made up of the project key plus a number (for example, PERIT3-2 means issue number 2 in project PERIT3). So the actual project key you need to use is just PERIT3, without…

Click Spaces -> Click Create Space -> Select Templates -> Use the IT Service Management template instead of the Development Request template

Hi @Saji Sasi This usually happens when a different template is selected while creating the project. If the "IT Service Management" template is used, all request types appear separately. Since the "Development requests" template was selected, some request types are grouped under Unassigned.

Hi @Komal Santosh Sudulwar It is not possible to create or replace the login page with a fully customized one, even when using Refined. The login and authentication process is managed by Atlassian, so third-party apps or plugins cannot modify or replace the Atlassian login screen. Refined only allows customization of the…

Hi @Uta Samaga In Confluence (free plan), it’s currently not possible to automatically update specific cells in a Page Properties table with values like page status or last editor using Automation. Automation cannot read or update values inside the Page Properties macro directly. Automation can still update page content in…

Hi @taylor Welcome to the Atlassian Community The easiest way to automate workflows is by using Jira Automation together with tools like Zapier or Make. For example, when someone submits a form (such as Google Forms or Typeform), the integration tool can automatically send that data to Jira and create a ticket. This helps…

Hi @Saji Sasi Welcome to the Atlassian Community Could you please share a screenshot of the issue? It will help me understand how the Assignee Group and Assignee fields are getting populated when the ticket is created.

@Grant Smith Please check the Story Points field context under Jira Settings -> Work items -> Custom fields -> Story Points -> Contexts and default values, to make sure it’s enabled for the Task issue type, since by default it’s often only available for Stories/Epics.

Are you using the same screen (Create/Edit/View screens) for all work types, or different screens for different work types?

Go to Jira Settings -> Work Item -> Field configurations, open the configuration used by the space, and make sure Story Points is not hidden for the Task work type.

Hi @Grant Smith If it’s a company-managed project, the most likely reason is that the Story Points field hasn’t been added to the issue screens used by the project. An admin can fix this by going to Jira Settings -> Issues -> Screens, opening the screen used by the project (Create/Edit/View), and adding the Story Points…

Hi @Grant Smith If you’re using a team-managed project in Jira Cloud, the “0 screens” message is normal because screens aren’t used to manage fields in this project type. Instead, go to Project settings -> Issue types -> select the issue type -> Add field -> “Story point estimate”, as team-managed projects use Story point…

Hi @Hardik Sharma , Welcome to the Atlassian Community Plans in Jira (previously called Advanced Roadmaps) help teams plan and organize work across multiple projects in one place. It gives a clear roadmap where teams can see what work needs to be done, who is responsible for it, and when it is expected to be completed.…

Hi @Pradeep Shetty Your login is working, but your account does not have access to Confluence for this site. Please contact your Confluence admin and ask them to give your account access.

Hi @Anubhav Agrawal On the Jira Cloud Free plan, permissions can’t be customized. This option is only available on Atlassian’s paid plans. Because of this limitation, only users who are space administrators can see and manage certain settings. If your colleague needs access to those options, you’ll need to give them…

Enric has shared screenshots above that show where to find these options, which should help locate the settings in the new UI.

Hi @Rupert Ward You’re not missing anything, Jira’s UI has changed. In team-managed Spaces, the Releases feature is no longer enabled from Space settings -> Features (that page now only shows options like Sprints, Estimation, and Standups). Instead, you enable Releases by adding it to the space navigation. Open your Space,…

Hi @koen , Welcome to the Atlassian Community The best way to use automation is to focus on reducing repetitive work while keeping the number of automation rules low. Instead of creating many small rules, it’s better to create a few well-structured rules with conditions that handle multiple situations. For example, you can…

It usually finishes within a few days, but in some cases Atlassian may take up to about 15 days to completely remove the subscription after it’s cancelled.