Mikael Sandberg Community Champion

Hi @Justin Fidler, Welcome to Atlassian Community! This is expected behavior, it has been like that since the inline comment was introduced in Confluence. You can still use Ctrl-C/Command-C to copy the text and then paste it somewhere else. 

@Shashank Agrawal This is a 6 year old question, you should consider creating your own question for this. I do not the answer to your question, 2020 was the last year I worked on Server/DC...

Yes, this is possible and what you need to do is set up work item security schemes. You can then use one for the work items that the user should be able to view, and the second one for work items they should be able to view. You can then use automation to set the security level, and I would use the one were the user cannot…

Hi @Dulanjali Peiris, Welcome to Atlassian community! Issue type is now called Work item, as announced in this post from May 2025. 

You can do this by setting up a new Authentication policy and set it to allow API token access and add your service accounts as members of the policy. Once that is done change the default one to block API token access to prevent users from creating tokens.

Yes, manage the page layout is a Premium plan feature as described in the documentation that you can find here.

In order to remove the priority field from the card you have to remove it from the field configuration that the project is using. Note that that this would remove the field from the work item layout as well.

Hi @Leandro Augusto de Souza Pachega, Welcome to Atlassian Community! You need to go to admin.atlassian.com, and if you are on the new centralized admin UI (all the menu options are on the left) click Billing and then Manage for the app you need the SEN for. This will bring up the Subscription screen and the SEN is listed…

You add comments and vote this feature request, AUTO-51

Hi cya-jiraappadmin-3@jackson.com, Welcome to Atlassian Community! Your only option right now would be to export your rules and then search the generated JSON file for what you are looking for. There is an API for automations, but it does not allow you to search for components within a rule. 

Hi @Heather Comfort Welcome to Atlassian Community! You do this by making the field required, either from with the request form like this example: Or by going to the field configuration scheme for your project and mark the field required. The difference is that if you do it from the request form the field will only be…

Your other option is to use {{issue.customfield_11756}} to set the assignee, that way you do not have to use the extra component to create the variable.

Your smart value component is missing the actual smart value you want to set. Your automation should look something like this to assign the sub-task to the manager:

Correct, and then add the fields you want on the request. Note that the fields do not have to have the same names as what the customer will see, so keep the field names as generic as possible, that way if you create custom fields they can be re-used in other projects if needed.

In that case I would just use the request form and not the Form option. The Form is suppose to compliment the request form, not replace it, and if you want to report on the data you would have to link each question in the form to a Jira field.

From admin, expand Apps > Sites to see your instances. Next under Site settings you should see Jira Service Management and Portal customers only And from here you can change the full name

Yes, everyone would be considered since it is based on the instance, not the number of users you enable SSO for. For individual apps Guard is included in the Enterprise plan.

I would start by taking a look at your SLA configuration to see if one of your goals are overlapping and causing the wrong SLA from being picked. 

Yes, you can disable the create button for a projected by changing the permission scheme the project is using so it no longer allow users to Create Issue If you make your forms public then you should be able to make the same change in the new project (try it out, I know it works in JSM, there you can set it so only portal…

Hi @Mike Marino, Welcome to Atlassian Community! This is a question that the vendor for Xray could answer, some of the information that Rovo would need to access lives within Xray which Rovo currently do not have access to. I know that Xray has its own AI but you would need Xray Enterprise in order to use it.

You can find information on is considered a billable user in this KB. Basically all managed accounts and external users count towards your bill unless you are on a plan that already include Guard, like Enterprise and Teamwork Collection Premium.

Go to admin.atlassian.com > Billing and from here locate Zephyr and click on Manage > Three dot menu at the top should have an option to cancel your subscription.

Okay, in the new centralized UI you have to click on Apps > Sites > your site and from here you will see Jira Service Management > Portal only customers. 

For portal only customers you have to go to admin.atlassian.com > Apps > Jira Service Management and from here you can lookup the customer and change their name.

Hi @Benjamin Gregory Moody, Welcome to Atlassian Community! What you are trying to do is not possible in a team-managed project, it can only be done in a company-managed project. 

@Ert Dredge Services is not dependent on Deployment tracking. Here is a screenshot from my free instance and I can create services on it.

Hi @mmolebatsi, Welcome to Atlassian Community! Once you created a custom field you cannot change the field type, so you only option is to create a new field to replace the existing one. 

The short answer is no, you cannot add more fields to the link work items screen. And the configure fields that you see in your Jira project would only allow you to add fields that are already on the screen, it will not allow you to add new ones.

It can be done via an automation, and you can trigger it on the transition to the specific status and then use the component called Change form status to open up the form for editing. I wrote an article that uses that component to display additional fields on the portal.

Hi @Edmond, Welcome to Atlassian Community! I have notified the Atlassian support team that is on here and they will reach out to you within 2 business days to get this resolved.