-
Bug
-
Resolution: Low Engagement
-
Low (View bug fix roadmap)
-
None
-
7.1.0, 6.4.12
-
None
-
6.04
-
1
-
Severity 3 - Minor
-
0
-
Summary:
In the development panel, the committer avatar is shown as the default avatar regardless of the user avatar at Bitbucket Server side.
Steps to Reproduce:
- Integrate JIRA with Bitbucket Server.
- Create a repo and make a commit with its commit message including an issue key on JIRA side.
- Let Bitbucket Server capture the commit.
- Create a user that uses the same email address as the committer, then specify a unique avatar.
- Navigate to the mentioned issue key in JIRA.
- Click the "Commits" link in the Development Panel.
Expected Result:
- As how bitbucket have mapped the committer account to Bitbucket Server account, the Avatar will be shown.
Actual Result:
- JIRA will still show the default Anonymous avatar beside the commits.
Notes:
- Tested in JIRA 7.1.0 and Bitbucket Server 4.1.0
- Tested with FerCru 4.0.3 and the avatar is shown when the committer is mapped with FerCru user.
| Form Name | |||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
[JSWSERVER-14802] Bitbucket Server Committer Avatar is using the default avatar
Edit; profile picture updated it's self a few hours later. Sorry, and thanks!
- I changed my username (Both versions are previously used usernames on different accounts)
- Bitbucket avatar reset to default, atlassin one stays fine.
- Changing avatar does not solve this issue.
- Profile picture updates it's self a few hours later
Hi,
At Atlassian, our goal is to ensure we’re providing the best experience for our customers. With our new Data Center strategy, Atlassian's focus is on security, compliance, and performance and is a key driver in prioritizing bugs. Closing the bugs that do not fall into those categories will allow us to focus on the ones in the most current versions of our products.
This bug is being closed due to a lack of engagement in the last four years, including no new watchers, votes, or comments; this inactivity suggests a low impact.
Please note the comments on this thread are not being monitored.
You can read more about our bug fix policy here and how we prioritize bugs.
To learn more about our recent investments in Jira Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Jira Data Center