• Type: Bug
• Resolution: Timed out
• Priority: Low (View bug fix roadmap)
• Fix Version/s: None
• Affects Version/s: 7.11.0
• Component/s: Navigation - View results
• Labels:

  None

1. 

   issue-edit-help.png

   68 kB

   12/Feb/2019 6:47 PM

2. 

   Screen Shot 2019-02-12 at 12.42.13 PM.png

   58 kB

   12/Feb/2019 6:43 PM

3. 

   Screen Shot 2019-02-12 at 12.43.08 PM.png

   179 kB

   12/Feb/2019 6:43 PM

[JRASERVER-68637] On an Issue when you click on Edit then click on the first ? for issue type the display is very large and not correct

Collapse comment: Ewelina Fiedorowicz added a comment - 22/Jul/2021 10:31 AM

Ewelina Fiedorowicz added a comment - 22/Jul/2021 10:31 AM

Atlassian Update – 22.07.2021

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 Time Out.

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 Jira 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 Atlassian Bugfix 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.

Thank you,
Ewelina Fiedorowicz

Expand comment: Ewelina Fiedorowicz added a comment - 22/Jul/2021 10:31 AM

Ewelina Fiedorowicz added a comment - 22/Jul/2021 10:31 AM Atlassian Update – 22.07.2021 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 Time Out . 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 Jira 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 Atlassian Bugfix 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. Thank you, Ewelina Fiedorowicz

Collapse comment: Michal Warkocz added a comment - 23/Jan/2019 1:02 PM

Michal Warkocz added a comment - 23/Jan/2019 1:02 PM

Hi estorch, Can you please provide some screenshots to help clarify the bug? Cheers, Michał, Jira Server Bugfix team

Expand comment: Michal Warkocz added a comment - 23/Jan/2019 1:02 PM

Michal Warkocz added a comment - 23/Jan/2019 1:02 PM Hi estorch , Can you please provide some screenshots to help clarify the bug? Cheers, Michał, Jira Server Bugfix team