feat(Integrations): Created a new page for the Atlassian integration #16632
Conversation
nbaenam
added
content
|
Hi @nbaenam 👋 Thanks for your pull request! Your PR is in a queue, and a writer will take a look soon. We generally publish small edits within one business day, and larger edits within three days. We will automatically generate a preview of your request, and will comment with a link when the preview is ready (usually 10 to 20 minutes). If you add any more commits, you can comment |
✅ Deploy Preview for docs-website-netlify ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Although it seems that some checks failed, this PR was built correctly: https://app.netlify.com/sites/docs-website-netlify/deploys/6627913e39670d0598ba13e7 |
src/content/docs/more-integrations/best-practices-integration.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/more-integrations/best-practices-integration.mdx
Outdated
Show resolved
Hide resolved
| It's important to understand this distinction when setting up an integration. For example, you may want to make sure about generating an API key from a user who has the correct permissions. You may want the user to only have access to certain accounts in the application. This limits what they can see and share with others. For example, say you have more users in your Atlassian application than in your New Relic accounts, and you configure the Atlassian integration. The users in the Atlassian integration will be able to see the New Relic data shared with Atlassian in the Atlassian application. Regardless of whether those users have access to the corresponding New Relic accounts. | ||
|
|
||
|
|
||
| ## Integration user leverage [#leverag-integration-user] |
There was a problem hiding this comment.
This title is likely accurate but it's a little confusing at first glance, anyway to clarify it?
src/content/docs/more-integrations/best-practices-integration.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/more-integrations/best-practices-integration.mdx
Outdated
Show resolved
Hide resolved
src/content/docs/more-integrations/best-practices-integration.mdx
Outdated
Show resolved
Hide resolved
...ocs/more-integrations/open-source-telemetry-integrations/atlassian/atlassian-integration.mdx
Outdated
Show resolved
Hide resolved
...ocs/more-integrations/open-source-telemetry-integrations/atlassian/atlassian-integration.mdx
Outdated
Show resolved
Hide resolved
...ocs/more-integrations/open-source-telemetry-integrations/atlassian/atlassian-integration.mdx
Outdated
Show resolved
Hide resolved
...ocs/more-integrations/open-source-telemetry-integrations/atlassian/atlassian-integration.mdx
Outdated
Show resolved
Hide resolved
|
|
||
| ## Enable the incidents tab [#enable-incidents-tab] | ||
|
|
||
| You may need to link to the Atlassian documentation. It walks a Jira site admin through enabling the Incidents tab and assigning it to a workspace. There is a chance they are going to enable by default and then, you won't need this section. |
There was a problem hiding this comment.
I notice that Incidents and incident tab and the like have some inconsistent capitalization that will need to be addressed
There was a problem hiding this comment.
"a chance they are going to enable by default" reads very awkwardly to me
...ocs/more-integrations/open-source-telemetry-integrations/atlassian/atlassian-integration.mdx
Outdated
Show resolved
Hide resolved
...ocs/more-integrations/open-source-telemetry-integrations/atlassian/atlassian-integration.mdx
Outdated
Show resolved
Hide resolved
|
I'm going to merge because this has been already reviewed by Jeff and 2 SMEs. |
PR to create a new page explaining how to integrate New Relic with Atlassian Jira.
This is the ticket: NR-236395