-
Suggestion
-
Resolution: Low Engagement
-
1
-
Hi everyone,
Thanks so much for your votes and comments on this feature request.
We've taken a good look at this feature along side the other top JIRA feature requests and unfortunately we won't be able to fit this into the JIRA roadmap for the next 12 months.
The development panel on the right hand side of the issue is the new way to view all information related to development on this issue. This contains related branches, commits, pull requests, builds, and deployments. Learn more here.
From your comments we believe the best fix would be to allow for related development activity to add to the activity tab rather than bring back the source tab. If there are other details that you believe wouldn't be covered by that fix, please add your scenario in the comments below.
Thanks for your patience and we hope you appreciate our open approach to feature requests.
Cheers,
Megan
Atlassian Product Management
mcook@atlassian.com
Original request description:
When this was removed, a lot of functionality was removed with it. Bring it back.
[JSWCLOUD-14929] Re-enable the source tab
Rashmi
added a comment - Whats the update on this issue? I am still seeing it disabled 
Sam Shen
added a comment - Can we fix it in a flexible way by using a "enable and disable" switch in settings.
I think FishEye Plugin already have "FishEye Issue Tab Panel" and "Crucible Issue Tab Panel" . But they are not working now.
Sam Shen
added a comment - Can we fix it in a flexible way by using a "enable and disable" switch in settings.
I think FishEye Plugin already have "FishEye Issue Tab Panel" and "Crucible Issue Tab Panel" . But they are not working now. Sam Shen
added a comment - One and half years have passed. Why this issue still "Unresolved" ?
Please fix it , we need it.
Sam Shen
added a comment - One and half years have passed. Why this issue still "Unresolved" ?
Please fix it , we need it. With all the focus Atlassian has on agile I'm very disappointed that you guys are not able to fit this feature request into the roadmap anytime soon.
Uwe Trenkner
added a comment - I totally agree with Alessio.
The new view is much more complicated than the traditional source tab. Did I remember right that in the 2.x version of the soucre tab you could see every diff in the jira ticket? This is what I am looking for.
Uwe Trenkner
added a comment - I totally agree with Alessio.
The new view is much more complicated than the traditional source tab. Did I remember right that in the 2.x version of the soucre tab you could see every diff in the jira ticket? This is what I am looking for. 
Alessio Nunzi
added a comment - We now put in place a workaround that I think is the one you suggested but without guarantee that the next version will still allow that.
Therefore I'd like you guys to keep in mind our issues when designing an improved development panel.
Alessio Nunzi
added a comment - We now put in place a workaround that I think is the one you suggested but without guarantee that the next version will still allow that.
Therefore I'd like you guys to keep in mind our issues when designing an improved development panel. 
Martin Sander
added a comment - If you use Fisheye, there is an easy workaround to get the source tab back. According to this KB article, the development tab is only used if the application link has 2-legged oauth enabled. So you can just configure your application link to use trusted apps and disable 2-legged oauth for it.
This is probably not what you want if you only have an application link to Stash, though..
Martin Sander
added a comment - If you use Fisheye, there is an easy workaround to get the source tab back. According to this KB article , the development tab is only used if the application link has 2-legged oauth enabled. So you can just configure your application link to use trusted apps and disable 2-legged oauth for it.
This is probably not what you want if you only have an application link to Stash, though.. Alessio Nunzi
added a comment - Hi guys, I find really hard use the new developer panel because of the following:
- the modal view that opens when you click on the “commits” link is really annoying given it prevents me from interacting with the rest of the page. (The Source tab allowed me to do so)
- the list of file involved is not complete as it used to be and I don’t want to open the full commit details in an other tool (we use FeCru) because it leads me away from the context of the ticket plus there’s no “expand-all” link to expand details of every commit at once.
- the commit messages are often truncated and visible only when hovering making impossible read them all at once.
Please try accomodate these needs into the next version.
Thanks in advance
Alessio Nunzi
added a comment - Hi guys, I find really hard use the new developer panel because of the following:
the modal view that opens when you click on the “commits” link is really annoying given it prevents me from interacting with the rest of the page. (The Source tab allowed me to do so)
the list of file involved is not complete as it used to be and I don’t want to open the full commit details in an other tool (we use FeCru) because it leads me away from the context of the ticket plus there’s no “expand-all” link to expand details of every commit at once.
the commit messages are often truncated and visible only when hovering making impossible read them all at once.
Please try accomodate these needs into the next version.
Thanks in advance 
Hi everyone,
Thank you for bringing this suggestion to our attention.
As explained in our new features policy, there are many factors that influence our product roadmaps and determine the features we implement. When making decisions about what to prioritize and work on, we combine your feedback and suggestions with insights from our support teams, product analytics, research findings, and more. This information, combined with our medium- and long-term product and platform vision, determines what we implement and its priority order.
Unfortunately, as a result of inactivity (no votes or comments for an extended period of time), this suggestion didn’t make it to the roadmap and we are closing it.
While this issue has been closed, our Product Managers continue to look at requests in https://jira.atlassian.com as they develop their roadmap, including closed ones. In addition, if you feel like this suggestion is still important to your team please let us know by commenting on this ticket.
Thank you again for providing valuable feedback to our team!