-
Bug
-
Resolution: Low Engagement
-
Low
-
None
-
5.7, 5.7.4
-
Windows 2012 Server / Testsystem / Atassian Standard installation
-
Severity 3 - Minor
-
If you upload a BIG Picture in your userprofile, you get an Error:
Redlined Box with white Contentbox - and there is WHITE text in it:
"There was an error uploading your imageThe selected image size is 4128px * 2322px. The maximum allowed image size is 2000px * 2000px"
-> You cant read it if you don't mark it.
[CONFSERVER-36948] Problem when uploading profile picture greater than 2000x2000px
| QA Demo Status | New: Not Needed [ 14332 ] | |
| QA Kickoff Status | New: Not Needed [ 14236 ] | |
| Resolution | New: Low Engagement [ 10300 ] | |
| Status | Original: Gathering Impact [ 12072 ] | New: Closed [ 6 ] |
| Labels | Original: affects-server user-profile | New: affects-server cleanup-seos-fy25 user-profile |
| Workflow | Original: JAC Bug Workflow v3 [ 2896491 ] | New: CONFSERVER Bug Workflow v4 [ 2989305 ] |
| Workflow | Original: JAC Bug Workflow v2 [ 2787851 ] | New: JAC Bug Workflow v3 [ 2896491 ] |
| Workflow | Original: JAC Bug Workflow [ 2736201 ] | New: JAC Bug Workflow v2 [ 2787851 ] |
| Symptom Severity | Original: Minor [ 14432 ] | New: Severity 3 - Minor [ 15832 ] |
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2390273 ] | New: JAC Bug Workflow [ 2736201 ] |
| Status | Original: Open [ 1 ] | New: Gathering Impact [ 12072 ] |
This is such a small detail, but it costed us days with a support case, as we couldn't even begin to imagine what was the exact problem the user was having.
The limit is pretty sane, but the lack of a visible error message is a pain.
| Workflow | Original: Confluence Workflow - Public Facing - Restricted v5 [ 2286509 ] | New: Confluence Workflow - Public Facing - Restricted v5 - TEMP [ 2390273 ] |
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 Confluence Data Center, please check our public roadmap and dashboards containing recently resolved issues, current work, and future plans.
Kind regards,
Confluence Data Center