-
Suggestion
-
Resolution: Unresolved
When uploading a new file to a code review, the file picker field is too wide when viewed in the Edge browser:
Other dialogs could be improved as well, e.g. 'Private key' on the repository settings tab:
[CRUC-8431] Improve look of the file upload picker in Edge
| Status | Original: Gathering Interest [ 11772 ] | New: Not Being Considered [ 11776 ] |
| Fix Version/s | New: N/A [ 54415 ] | |
| Labels | Original: checked-for-duplicates edge | New: checked-for-duplicates edge jac-cleanup-phase10 |
| Labels | Original: edge | New: checked-for-duplicates edge |
| Description |
Original:
When uploading a new file to a code review, the file picker field is too wide when viewed in the Edge browser:
!edge-add-content-upload.png|thumbnail! Other dialogs could be improved as well, e.g. repository settings: !edge-drop-down-and-file-upload.png|thumbnail! |
New:
When uploading a new file to a code review, the file picker field is too wide when viewed in the Edge browser:
!edge-add-content-upload.png|thumbnail! Other dialogs could be improved as well, e.g. 'Private key' on the repository settings tab: !edge-drop-down-and-file-upload.png|thumbnail! |
| Description |
Original:
When uploading a new file to a code review, the file picker field is too wide when viewed in the Edge browser:
!edge-add-content-upload.png|thumbnail! |
New:
When uploading a new file to a code review, the file picker field is too wide when viewed in the Edge browser:
!edge-add-content-upload.png|thumbnail! Other dialogs could be improved as well, e.g. repository settings: !edge-drop-down-and-file-upload.png|thumbnail! |
| Attachment | New: edge-drop-down-and-file-upload.png [ 379804 ] |
| Labels | New: edge |
Hi everyone,
We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Not Being Considered.
Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Fisheye&Crucible team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Implementation of New Features Policy for more details.
We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
Kind regards
Marek Parfianowicz
Development Team Lead