Overview
Correct user attribution is a critical component of keeping your issues organized. With Integration+ all updates in Jira are from the user who performed the action
...
, not a "bot" user.
What to know
All updates will have correct user attribution in Jira.
Users connect their Slack and Jira accounts to make updates to Jira.
Users' Jira permissions are automatically respected by Integration+.
On this page:
|
|---|
How does it work?
...
A user mentions a Jira issue in a channel where the bot is invited.
The bot responds with issue information.
The user chooses the comment action to add a comment.
The comment
...
was added to Jira as the user who added the comment
...
to Slack.
What is happening in the technology?
We use OAuth to communicate with the Jira APIs, and users
...
must authenticate with Jira to allow our systems to
...
update Jira on their behalf. This process is
...
known as API impersonation.
The result is that all updates made from Integration+ are reflected in Jira as the user who performed the action. This ensures the source of the update (Slack / Jira / Email
...
) does not
...
affect Jira tracking
...
.
User connections
The first time users interact with the app, they will be automatically
...
required to connect their Slack account with their Jira account to establish connectivity and permissions in Jira.
What to know
Your password is never shared with our systems
Every action you take in Slack (create, comment
...
) will
...
be attributed to your Jira account
...
.
Your permissions are based on your Jira access.
...
You will be asked to connect your account when
...
performing your first action in Slack. You can also manually trigger the connection by typing /jira-plus connect.
Click
...
Connect Now
...
in Slack.
Click Allow in Jira.
Click the button to go to the home screen in Slack.