Ivan Lima Expert

Yes. In Jira DC, you can analyze the usage of custom fields. Some apps can help you with that too. See managing custom fields in Jira effectively for more details where you can find a few suggested apps and database queries.

Are you trying to use Atlassian connect/Forge? To my knowledge, you can't use OAuth (3LO) to create users. In this case, you need to use basic auth (email + api_token). Have a look at how Atlassian handles user provisioning via API.

Welcome to the Atlassian Community! Yes. You need to use "representation": "wiki". See Create content API for more details.

Welcome to Atlassian Community. There are a few reasons why you're getting this error message. I found similar posts that can give you some insights into that. Have a look. * https://community.atlassian.com/t5/Jira-Software-questions/POST-rest-api-3-issue-OAuth-2-0-is-not-enabled-for-this-method/qaq-p/1760866 *…

You don't need to change the properties; Jira does it for you. The "Approved" button you see is your transition. Once you hit the "First Approved" status, you should repete the approval configuration the same way you did for the "Waiting for Approval" status. Focus on getting the first one to work as expected so you fully…

Fields is a shortcut for calling update with the set operation. See more details here. I'd suggest breaking your implementation into smaller steps so you can resolve one piece at a time. For a single-select custom field, you should be using the following: "customfield_11449" : { "value": "option3" } or "customfield_11449"…

Hi @Mike Singleton, here is a similar post where you can get some insights into implementing it using Automation for Jira. Have a look, and let us know if you can apply it to your use case. * https://community.atlassian.com/t5/Jira-Service-Management/How-to-set-a-field-value-based-on-other-custom-field-value/qaq-p/1773343 

Hi @Clarisse. Welcome to the Atlassian Community! You can't yet customize the fields shown on cards in team-managed projects. See a similar post here and more details on the following feature request: * https://jira.atlassian.com/browse/JSWCLOUD-17336

I tested it myself, and it turns out that userkey works, but the account id doesn't. You can get the userkey by mentioning a user on a page, publishing it, and accessing the "view storage format" settings (More actions > Advanced details > View Storage Format). I know Atlassian is deprecating username and userkey from the…

Yeah, this is definitely a FF topic. I haven't thought about it, but the "mate" one is extremely popular in southern Brazil. Looking at my frequently used ones, they're pretty standard. I feel like it saves me a lot of time sometimes. I need to catch up on the emoji dialects, the new ones, to get updated with the new…

You can't yet reference issue attachments in the new issue view. There is an open request to implement that. You can temporarily switch the old issue view to do that. * https://jira.atlassian.com/browse/JRACLOUD-72208

Hi @ELI0067. Welcome to the Atlassian Community! It sounds like you're on the right path. Have you double-checked the transitions and permissions and tried isolating the steps? Is the "transition when approved" set to the one intended to? You can create multiple approval transitions, and they work the same way.

Hi @María Cabrera, are you using the account id for the userkey? Try that instead; it should work. You can mention someone and view the storage format of the page to confirm the syntax. <ac:link><ri:user ri:userkey="8a7f808a7******************eb330006"/></ac:link>

Hi @Vishal, have you tried adding the target attribute to your help text? Try this: <a href=\"https://xxxxx.com/\" target=\"_blank\">Link</a>

Yes, not yet supported.

Hi @Vinay Sharma, do you mean to sync your groups and settings? You can set up G Suite to do that. Have you tried that?

Yes, but service management project types are not yet supported. You can use the cloud-to-cloud migration tool and apps such as Configuration Manager for Jira (Server-to-Cloud). For reference: * Prepare sites for a cloud-to-cloud migration * What migrates in a cloud-to-cloud migration for Jira * Configuration Manager for…

Hi @Vera. Welcome to the Atlassian Community. You need to use APIs in this case. The CSV export/import doesn't handle remote links. I found the following feature request at the Atlassian public issue tracker: * Remote and web links are not handled in JIM For reference: * respect remote issue links during CSV import *…

Hi @Vinay Sharma, you can’t restrict knowledge base articles per organization out of the box. You might find an app to help you to achieve that. Besides the KB access segregation, are there other requirements you need similar behaviour between internal and external customers? For reference, see related links: *…

There are a few ways to think of how you can do that—for example, creating a board with an underlying filter that combines both projects. There're caveats like agents with access to both service projects, etc. A dashboard will also do it if you're interested in monitoring only.

You can undoubtedly automate this, but you'd need to spend some time implementing that, and I wound't advise you to do that—especially if you're moving to Atlassian Cloud later anyways. You can either export your issues using CSV and import them on the cloud or use an app to handle that for you, which is much better.…

The customer permissions settings. Go to Project Settings > Customer permissions > Who can customers share requests with? To allow customers to remove other customers, you need to select any option other than "Other customers in their organization".

Hi @Kai Krause, customers should be able to remove participants. Which version are you in, and what's your customer permissions configuration?

Hi @Allen Tong. Welcome to the Atlassian Community! You can copy a numeric custom field value to the original estimate system field using Automation for Jira. What have you tried so far? If you can share your setup, we can better assist you here.

I don't believe so. To my knowledge, there isn't an attachment attribute type that you can set to display on the issue view. You can, though, create another insight object type modelling your own "attachment" insight object.

You cannot restrict the number of attachments the way you want to. You need an app, or a script likely does it. You can configure some advanced settings for zip files, for example. For more details, see Configuring file attachments.

Another possible solution would be removing the permission to link issues using workflow properties. However, it will apply to all issue types associated with the workflow, so you have to isolate it if you want that to be enforced for epics only. * Workflow properties * Can we disable linking issues to an Issue when it is…

Okay, so the trigger is the "issue created" event, and then you have your logic around the cascade custom field to send the notification. I assume you already have an action to send the email. From an implementation perspective, you could have something like: Value of the parent: {{issue.fields.Cascade.value}} Value of the…

There are a few options I can think of to implement this, but depending on the number of cascade options, it can be cumbersome to maintain as a cascade select list. What is the trigger for the notification? Ideally, you could design a solution using a user picker type of field to make it easier to send notifications.

You can, observing what I mentioned initially. For the second part of your question: Only JSM agents will be counted towards your Atlassian Access bill. Portal-only customers are not billable for Atlassian Access unless they have product access to another Atlassian Access supported product. For more details, see Manage…