nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Has Development panel replaced the Source/Review tab?

fmeira

Hi,

can someone confirm this or explain me how to get both enabled?

I have recently upgraded to Jira 6.2 and FishEye 3.4 and Source tab was fine but the new Developement Panel was not configured (missing OAuth 2LO).

When I configured that, I got the Developement Panel working fine, but lost the Source and Review tabs. At this point, my users prefer to keep the Source/Review tabs so I would like to either revert these changes or have both enabled.

So, is the development panel a replacement for the Source/Review tabs? Can we have them both enabled? If so, how?

Thanks

Accepted answers

Pedro Souza

Hello Fernando,

According to our release notes:

https://confluence.atlassian.com/display/JIRA/JIRA+6.2+Release+Notes

All the tabs related to Development tools were replaced by the Development Panel.

As far as I know there is no way to enable the tabs instead of using the new feature.

Cheers,

Pedro Souza.

All comments

Pedro Souza

Hello Fernando,

According to our release notes:

https://confluence.atlassian.com/display/JIRA/JIRA+6.2+Release+Notes

All the tabs related to Development tools were replaced by the Development Panel.

As far as I know there is no way to enable the tabs instead of using the new feature.

Cheers,

Pedro Souza.

Aaron Carlson

I would also like to know how to get both enabled. The development panel doesn't function like the source tab and is virtually useless for the things I was able to do with the source tab (such as quickly view diffs). Really hoping there is a quick way to re-enable the source tab!

I created a ticket to track this JRA-38087

Nick

@AaronCalrson - the Development Panel should let you do everything and more than the old source tab.

To get links to diffs for each file in the changeset, ensure you are 'viewing files' in the dev panel.

See: http://monosnap.com/image/GVycjGtVPn2Ql4D2qfrfS6MhGbxO2R.png

Aaron Carlson

Yes, I clicked the Show Files link, but it doesn't show the inline diffs (it doesn't show them in your picture either).

Look at this: http://blogs.atlassian.com/wp-content/uploads/jira-fisheye-source-tab.jpg

See the triangle next to each file? You can click that and see the inline diff instantly, without leaving JIRA. I can click it for all the files and easily see what the changes were, which is great!

You do get a link to FishEye which you have to click and leave JIRA to see the diff, but it isn't inline.

To go through several diffs via the development panel, you must click the link, then go to FishEye, then go back in the browser which makes the development panel popup disappear, which means clicking the "Commits" link, then "Show Files", then click the link to go back into FishEye, etc.

Nick

Can you please show me a screenshot of the inline diff you are referring to.

Also, which version of the JIRA FishEye Plugin are you using ?

Aaron Carlson

The diff shows up right below the filename with the icons next to it and looks very similar to the diff in FishEye. We have already upgraded to JIRA 6.2 and FishEye 3.3, so I can't get a screenshot of it. You should be able to load an instance of JIRA 6.1 with the source tab enabled and see what I'm talking about.

Jiri Zahradka

was the Source panel realy replaced with Development panel? Because on the screenshot from release notes we can see both. Asking because devel panel is not showing up in my jira 6.2.

Lee Latham

Definitely agree with this, it's a big step backwards in functionality. Several of my teammates agree. You have to keep going back to the main page, and you can't just click on a delta like before which was *very good*.

Sten Pittet

Hi,

The Development Panel is the replacement for the previous Source and Reviews tabs. The main reason for this change is to allow developers to have an overview of the state of an issue at a glance. We wanted to make sure that you wouldn't have to scroll to answer the following questions:

- Have we started to write code for this issue?
- Does it have a review?
- Do we have a build?

We also wanted to bring more alignment between the different source solutions. For customers having hybrid environment with Git and other SCMs and using Stash or Bitbucket along FishEye/Crucible we wanted to make sure that all information could be gathered in a practical way. This resulted in the Development Panel that we implemented today.

Your feedback is valuable for us to keep improving the user experience. We will keep on iterating on our approach but we believe that this is the best way forward for our customers. If you have more feedback or questions do not hesitate to communicate it to us.

Regards,

Sten Pittet
Dev Tools Product Manager

Jobin Kuruvilla [Adaptavist]

I like the development panel exactly for the reasons mentioned above. But lack of inline diff is a step backward. And I get that feedback whenever I show the demos. Is that something that will come back? On the popoup screens?

Ruchi Tandon

Sorry to hear that you all do not like the Development panel. Could you please try to disable the system plugin : "Atlassian JIRA - Plugins - Development Integration Plugin". That should block the development panel and as soon as the dev panel is not displayed, the Source tab should come back.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

fisheye-crucible