Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-9236

As a user I would like to resize the Detail View in Work mode

    • 182
    • 11
    • Hide
      Atlassian Update – 29 January 2019

      Hi everyone,

      I'm happy to announce that this feature is coming to you shortly with Jira 8.1, together with a larger set of improvements for Jira boards. If you have any questions or feedback, feel free to reach out to us in the comments.

      Kind regards,
      Sylwia Mikolajczuk
      Jira Server Team

      Show
      Atlassian Update – 29 January 2019 Hi everyone, I'm happy to announce that this feature is coming to you shortly with Jira 8.1, together with a larger set of improvements for Jira boards. If you have any questions or feedback, feel free to reach out to us in the comments. Kind regards, Sylwia Mikolajczuk Jira Server Team
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      NOTE: This suggestion is for JIRA Software Server. Using JIRA Software Cloud? See the corresponding suggestion.

          Form Name

            [JSWSERVER-9236] As a user I would like to resize the Detail View in Work mode

            I'm sorry to hear this feature is unavailable to you. It may be so if you use IE11, as it's not supported. Let me know if that's the case.

            Sylwia Mikołajczuk added a comment - I'm sorry to hear this feature is unavailable to you. It may be so if you use IE11, as it's not supported. Let me know if that's the case.

            Because it's Atlassian.  They just close tickets. I wish I could get away with that.

            mike.daigle added a comment - Because it's Atlassian.  They just close tickets. I wish I could get away with that.

            PwrSrg added a comment -

            This still doesn't exist.  WHY is this closed?  😑

            PwrSrg added a comment - This still doesn't exist.  WHY is this closed ?  😑

            19ee5130dd2f I'm not sure if I understand your question. The suggestion was to allow resizing the details view in work mode (sprint view) the same way as it was already working in backlog. It's done for Jira 8.1 and newer. What other details do you wish to know exactly?

            Sylwia MikoÅ‚ajczuk added a comment - 19ee5130dd2f  I'm not sure if I understand your question. The suggestion was to allow resizing the details view in work mode (sprint view) the same way as it was already working in backlog. It's done for Jira 8.1 and newer. What other details do you wish to know exactly?

            How is this fixed?  Is it in some other quantum universe?  Zero explanation from Atlassian how this is fixed. This is extremely frustrating. 

            Tom Gaffney added a comment - How is this fixed?  Is it in some other quantum universe?  Zero explanation from Atlassian how this is fixed. This is extremely frustrating. 

            It seems that Atlassian fixed that in Jira 8.1, but unfortunately only partly.

            We use custom fields of type "multiline textfield", It seems that they still have a fxed witdth and are not resized with the details view. Will Atlassian fix that, too?

            Dominik Haag added a comment - It seems that Atlassian fixed that in Jira 8.1, but unfortunately only partly. We use custom fields of type "multiline textfield", It seems that they still have a fxed witdth and are not resized with the details view. Will Atlassian fix that, too?

            Sylwia Mikołajczuk added a comment - - edited

            Hi saad.fahim, yes, we're working on this and it'll be available sooner than you think

            As for your other questions, I'll need some more details on what exactly do you want to know?

            Sylwia Mikołajczuk added a comment - - edited Hi saad.fahim , yes, we're working on this and it'll be available sooner than you think As for your other questions, I'll need some more details on what exactly do you want to know?

            Saad added a comment -

            @sylwia ...please can this be implemented for Jira Service Desk Agile boards too?

            Saad added a comment - @sylwia ...please can this be implemented for Jira Service Desk Agile boards too?

            Saad added a comment -

            Hi..Is Altlassian putting in a fix for this?

             

            How does the CSS work in Chrome?

            Saad added a comment - Hi..Is Altlassian putting in a fix for this?   How does the CSS work in Chrome?

            wattydev added a comment - - edited

            I adjusted @Ron Boerdman's code to fix an issue. After clicking on the bookmarklet, the pane's width is set to the same width you used before. But when you drag it, it resets to the Jira default, then starts dragging from there. This version makes the initial dragging smoother:

            javascript: {
              var dragBar = document.getElementById("ghx-detail-head");
              var detailView = document.getElementById("ghx-detail-view");
              var headerGroup = document.getElementById("ghx-column-header-group");
              var defaultHeaderWidth = headerGroup.clientWidth;
              var defaultDetailWidth = detailView.clientWidth;
              var controlGroup = document.getElementById("ghx-detail-head");
              var tmpElem = document.createElement("div");
              tmpElem.innerHTML =
                '<span style="display: block;" id="js-sizer" class="ghx-sizer ui-resizable-handle ui-resizable-w" data-tooltip="Resize Detail View" original-title=""><span class="ghx-icon ghx-icon-sizer"></span></span>';
              var dragElem = tmpElem.childNodes[0];
              controlGroup.insertBefore(dragElem, controlGroup.childNodes[0]);
              var currentWidth = localStorage.getItem("jiraWidth") || "400px";
              var currentStylesheet = document.createElement("style");
              currentStylesheet.innerHTML = `
                #ghx-detail-view {
                    width: ${currentWidth} !important;
                }
                #ghx-column-header-group {
                    width: calc(${defaultHeaderWidth}px - ${currentWidth} + ${defaultDetailWidth}px) !important;
                }
              `;
              document.body.insertBefore(currentStylesheet, document.body.childNodes[0]);
              dragBar.addEventListener("mousedown", startJiraDrag, false);
              var stateMouseDown = false;
              var mouseStartX = 0;
              var jiraStartWidth, jiraHeaderWidth;
              var currentStylesheet;  function startJiraDrag(ev) {
                jiraStartWidth = detailView.clientWidth;
                jiraHeaderWidth =
                  defaultHeaderWidth - (jiraStartWidth - defaultDetailWidth);
                detailView.style.width = jiraStartWidth + "px";
                headerGroup.style.width = jiraHeaderWidth + "px";
                if (currentStylesheet) {
                  document.body.removeChild(currentStylesheet);
                }
                stateMouseDown = true;
                mouseStartX = ev.pageX;
                document.addEventListener("mousemove", continueJiraDrag, false);
                document.addEventListener("mouseup", endJiraDrag, false);
              }  function continueJiraDrag(ev) {
                var pX = ev.pageX;
                detailView.style.width = jiraStartWidth + mouseStartX - pX + "px";
                headerGroup.style.width = jiraHeaderWidth - mouseStartX + pX + "px";
              }  function endJiraDrag() {
                currentStylesheet = document.createElement("style");
                currentStylesheet.innerHTML =
                  "#ghx-detail-view { width: " + detailView.style.width + " !important;} ";
                document.body.insertBefore(currentStylesheet, document.body.childNodes[0]);
                localStorage.setItem("jiraWidth", detailView.style.width);
                document.removeEventListener("mousemove", continueJiraDrag, false);
                document.removeEventListener("mouseup", endJiraDrag, false);
              }
            }
            void 0;
            

            wattydev added a comment - - edited I adjusted @Ron Boerdman's code to fix an issue. After clicking on the bookmarklet, the pane's width is set to the same width you used before. But when you drag it, it resets to the Jira default, then starts dragging from there. This version makes the initial dragging smoother: javascript: { var dragBar = document.getElementById( "ghx-detail-head" ); var detailView = document.getElementById( "ghx-detail-view" ); var headerGroup = document.getElementById( "ghx-column-header-group" ); var defaultHeaderWidth = headerGroup.clientWidth; var defaultDetailWidth = detailView.clientWidth; var controlGroup = document.getElementById( "ghx-detail-head" ); var tmpElem = document.createElement( "div" ); tmpElem.innerHTML = '<span style= "display: block;" id= "js-sizer" class= "ghx-sizer ui-resizable-handle ui-resizable-w" data-tooltip= "Resize Detail View" original-title= ""><span class=" ghx-icon ghx-icon-sizer"></span></span>' ; var dragElem = tmpElem.childNodes[0]; controlGroup.insertBefore(dragElem, controlGroup.childNodes[0]); var currentWidth = localStorage.getItem( "jiraWidth" ) || "400px" ; var currentStylesheet = document.createElement( "style" ); currentStylesheet.innerHTML = ` #ghx-detail-view { width: ${currentWidth} !important; } #ghx-column-header-group { width: calc(${defaultHeaderWidth}px - ${currentWidth} + ${defaultDetailWidth}px) !important; } `; document.body.insertBefore(currentStylesheet, document.body.childNodes[0]); dragBar.addEventListener( "mousedown" , startJiraDrag, false ); var stateMouseDown = false ; var mouseStartX = 0; var jiraStartWidth, jiraHeaderWidth; var currentStylesheet; function startJiraDrag(ev) { jiraStartWidth = detailView.clientWidth; jiraHeaderWidth = defaultHeaderWidth - (jiraStartWidth - defaultDetailWidth); detailView.style.width = jiraStartWidth + "px" ; headerGroup.style.width = jiraHeaderWidth + "px" ; if (currentStylesheet) { document.body.removeChild(currentStylesheet); } stateMouseDown = true ; mouseStartX = ev.pageX; document.addEventListener( "mousemove" , continueJiraDrag, false ); document.addEventListener( "mouseup" , endJiraDrag, false ); } function continueJiraDrag(ev) { var pX = ev.pageX; detailView.style.width = jiraStartWidth + mouseStartX - pX + "px" ; headerGroup.style.width = jiraHeaderWidth - mouseStartX + pX + "px" ; } function endJiraDrag() { currentStylesheet = document.createElement( "style" ); currentStylesheet.innerHTML = "#ghx-detail-view { width: " + detailView.style.width + " !important;} " ; document.body.insertBefore(currentStylesheet, document.body.childNodes[0]); localStorage.setItem( "jiraWidth" , detailView.style.width); document.removeEventListener( "mousemove" , continueJiraDrag, false ); document.removeEventListener( "mouseup" , endJiraDrag, false ); } } void 0;

            That this is not possible is so frustrating. It now takes a tiny size on the side of a large wide monitor. 

            Sander Pilon added a comment - That this is not possible is so frustrating. It now takes a tiny size on the side of a large wide monitor. 

            Imane Assoud added a comment - - edited

            Hello,

            Being able to resize the issue details view on "Work" mode is very useful for all Agile board customers, please accelerate the implementation of this feature.

            Regards,

             

            Imane Assoud added a comment - - edited Hello, Being able to resize the issue details view on "Work" mode is very useful for all Agile board customers, please accelerate the implementation of this feature. Regards,  

            This is unbelievably frustrating, how can the team at Atlassian force view options on Cloud users which are completely unfit for purpose! The narrow issue view is diabolical. Fix it!

            Rohan Sherrard added a comment - This is unbelievably frustrating, how can the team at Atlassian force view options on Cloud users which are completely unfit for purpose! The narrow issue view is diabolical. Fix it!

            Raju Kadam added a comment -

            Here is easy workaround that I'm using to take care of this problem for me:

            • install Firefox addon Custom Style Script as mentioned earlier.
            • Paste this one line css
            #ghx-detail-view{
            width:700px !important;
            }
            • And it works as I want
            • Big thanks to previous commenters on providing idea of using Custom Style Script add on in FireFox. I just moved back to FF from Chrome and couldn't be more happier

            Raju Kadam added a comment - Here is easy workaround that I'm using to take care of this problem for me: install Firefox addon Custom Style Script as mentioned earlier. Paste this one line css #ghx-detail-view{ width:700px !important; } And it works as I want Big thanks to previous commenters on providing idea of using Custom Style Script add on in FireFox. I just moved back to FF from Chrome and couldn't be more happier

            +1 – this is a major frustration for my team. I am unable to edit tickets effectively in such a small pane.

            Alexander Frieden added a comment - +1 – this is a major frustration for my team. I am unable to edit tickets effectively in such a small pane.

            This reminds me of Drag and Drop for sub-tasks (JRASERVER-24547). It took Atlassian 7 years to implement. Both tickets have about the same vote count at this point. I deduce that we will see this feature implemented by 2020! Hang in there, folks. Just two more years to go!

            Samuel Ecko added a comment - This reminds me of Drag and Drop for sub-tasks ( JRASERVER-24547 ). It took Atlassian 7 years to implement. Both tickets have about the same vote count at this point. I deduce that we will see this feature implemented by 2020! Hang in there, folks. Just two more years to go!

            Hi everyone,

            Thanks for your interest in this issue.
            This request is considered a potential addition to our longer-term roadmap.

            We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status.

            For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including:

            • Performance and stability improvements
            • Archiving projects for improved performance
            • Optimising the use of custom fields
            • Improving performance of boards
            • Improving Jira notifications
            • Allowing users to edit shared filters and dashboards
            • Mobile app for Jira Server

            You can learn more about our approach to highly voted server suggestions here.

            To learn more on how your suggestions are reviewed, see our updated workflow for server feature suggestions.

            Kind regards,
            Jira Server Product Management

            Kasia Derenda added a comment - Hi everyone, Thanks for your interest in this issue. This request is considered a potential addition to our longer-term roadmap. We'll typically review this request in about 12 months time, at which point we’ll consider whether we need to alter its status. For the nearest future we've decided to prioritize other areas of the Jira Server roadmap, including: Performance and stability improvements Archiving projects for improved performance Optimising the use of custom fields Improving performance of boards Improving Jira notifications Allowing users to edit shared filters and dashboards Mobile app for Jira Server You can learn more about our  approach to highly voted server suggestions here . To learn more on how your suggestions are reviewed, see our  updated workflow for server feature suggestions . Kind regards, Jira Server Product Management

            it_admin added a comment -

            @rob106 added a comment - 05/Jan/2015 11:55 AM - edited

            it's very usful. Here I add more detail for newer.

            1. install firefox addon Custom Style Script 
            2. paste below code in configuration for the website of jira
            // code placeholder
            function installMissedSplitbar(){    var dragBar = document.getElementById("ghx-detail-head");    var detailView = document.getElementById("ghx-detail-view");    var headerGroup = document.getElementById("ghx-column-header-group");    var controlGroup = document.getElementById("ghx-detail-head");    var tmpElem = document.createElement('div');    tmpElem.innerHTML = '<span style="display: block;" id="js-sizer" class="ghx-sizer ui-resizable-handle ui-resizable-w" data-tooltip="Resize Detail View" original-title=""><span class="ghx-icon ghx-icon-sizer"></span></span>';    var dragElem = tmpElem.childNodes[0];    controlGroup.insertBefore(dragElem, controlGroup.childNodes[0]);     var currentWidth = localStorage.getItem('jiraWidth') || '400px';    currentStylesheet = document.createElement('style');    currentStylesheet.innerHTML = '#ghx-detail-view { width: ' + currentWidth + ' !important;}';     document.body.insertBefore(currentStylesheet, document.body.childNodes[0]);     dragBar.addEventListener("mousedown", startJiraDrag, false);    var stateMouseDown = false;    var mouseStartX = 0;    var jiraStartWidth, jiraHeaderWidth;    var currentStylesheet;     function startJiraDrag(ev) {        if (currentStylesheet) {            document.body.removeChild(currentStylesheet);        }         stateMouseDown = true;        mouseStartX = ev.pageX;        jiraStartWidth = detailView.clientWidth;        jiraHeaderWidth = headerGroup.clientWidth;        document.addEventListener("mousemove", continueJiraDrag, false);        document.addEventListener("mouseup", endJiraDrag, false);    }     function continueJiraDrag(ev) {        var pX = ev.pageX;        detailView.style.width = (jiraStartWidth + mouseStartX - pX) + "px";        headerGroup.style.width = (jiraHeaderWidth - mouseStartX + pX) + "px";    }     function endJiraDrag() {        currentStylesheet = document.createElement('style');        currentStylesheet.innerHTML = '#ghx-detail-view { width: ' + detailView.style.width + ' !important;}';        document.body.insertBefore(currentStylesheet, document.body.childNodes[0]);        localStorage.setItem('jiraWidth', detailView.style.width);         document.removeEventListener("mousemove", continueJiraDrag, false);        document.removeEventListener("mouseup", endJiraDrag, false);    }};window.addEventListener("load", installMissedSplitbar,false);
            

            it_admin added a comment - @ rob106 added a comment - 05/Jan/2015 11:55 AM - edited it's very usful. Here I add more detail for newer. install firefox addon Custom Style Script  paste below code in configuration for the website of jira // code placeholder function installMissedSplitbar(){     var dragBar = document.getElementById( "ghx-detail-head" );     var detailView = document.getElementById( "ghx-detail-view" );     var headerGroup = document.getElementById( "ghx-column-header-group" );     var controlGroup = document.getElementById( "ghx-detail-head" );     var tmpElem = document.createElement( 'div' );    tmpElem.innerHTML = '<span style= "display: block;" id= "js-sizer" class= "ghx-sizer ui-resizable-handle ui-resizable-w" data-tooltip= "Resize Detail View" original-title= ""><span class=" ghx-icon ghx-icon-sizer "></span></span>' ;     var dragElem = tmpElem.childNodes[0];    controlGroup.insertBefore(dragElem, controlGroup.childNodes[0]);      var currentWidth = localStorage.getItem( 'jiraWidth' ) || '400px' ;    currentStylesheet = document.createElement( 'style' );    currentStylesheet.innerHTML = '#ghx-detail-view { width: ' + currentWidth + ' !important;}' ;     document.body.insertBefore(currentStylesheet, document.body.childNodes[0]);     dragBar.addEventListener(" mousedown ", startJiraDrag, false );     var stateMouseDown = false ;     var mouseStartX = 0;     var jiraStartWidth, jiraHeaderWidth;     var currentStylesheet;     function startJiraDrag(ev) {         if (currentStylesheet) {            document.body.removeChild(currentStylesheet);        }         stateMouseDown = true ;        mouseStartX = ev.pageX;        jiraStartWidth = detailView.clientWidth;        jiraHeaderWidth = headerGroup.clientWidth;        document.addEventListener(" mousemove ", continueJiraDrag, false );        document.addEventListener(" mouseup ", endJiraDrag, false );    }     function continueJiraDrag(ev) {         var pX = ev.pageX;        detailView.style.width = (jiraStartWidth + mouseStartX - pX) + " px ";        headerGroup.style.width = (jiraHeaderWidth - mouseStartX + pX) + " px ";    }     function endJiraDrag() {        currentStylesheet = document.createElement( 'style' );        currentStylesheet.innerHTML = '#ghx-detail-view { width: ' + detailView.style.width + ' !important;}' ;        document.body.insertBefore(currentStylesheet, document.body.childNodes[0]);        localStorage.setItem( 'jiraWidth' , detailView.style.width);         document.removeEventListener(" mousemove ", continueJiraDrag, false );        document.removeEventListener(" mouseup ", endJiraDrag, false );    }};window.addEventListener(" load", installMissedSplitbar, false );

            We suffered severly under too narrow custom textfields in the issue detail view pane due to not being able to resize that thing! We use a workaround of custom CSS styling which we have put in the announcement banner. Remember to adjust the ID of the custom field in the following stylesheet with your own's. We hope it helps someone. Works fine with Jira 7.6.2.

            <style type="text/css">
            /** This css fixes SQA-33 in a board's working mode. */
            .ghx-detail-view #rowForcustomfield_10111 .wrap {
              padding-left:0 !important;
              margin-top:2em !important;
            }
            
            .ghx-detail-view #rowForcustomfield_10111 .name {
              margin-left: 0 !important;
              margin-top:-2em !important;
            }
            </style>
            

            Richard Kiefer (JAM Software) added a comment - - edited We suffered severly under too narrow custom textfields in the issue detail view pane due to not being able to resize that thing! We use a workaround of custom CSS styling which we have put in the announcement banner. Remember to adjust the ID of the custom field in the following stylesheet with your own's. We hope it helps someone. Works fine with Jira 7.6.2. <style type= "text/css" > /** This css fixes SQA-33 in a board's working mode. */ .ghx-detail-view #row Forcustomfield_10111 .wrap { padding-left :0 !important ; margin-top :2em !important ; } .ghx-detail-view #row Forcustomfield_10111 .name { margin-left : 0 !important ; margin-top :-2em !important ; } </style>

            Quelyn added a comment -

            Would really like this feature, as I am working on a larger monitor and have the real estate to work this way if I could just make the pane larger. 

            Quelyn added a comment - Would really like this feature, as I am working on a larger monitor and have the real estate to work this way if I could just make the pane larger. 

            I strongly support the idea of having the possibility to resize the Detail View. But even better would be to choose if I want JIRA to show it just next to the board as it is or to show it as an overlay just when I create a task. The latter would even be way better for me because on my "small" FullHD screen I find it very uncomfortable to read the issues in that narrow column.

            Stefan Zauner added a comment - I strongly support the idea of having the possibility to resize the Detail View. But even better would be to choose if I want JIRA to show it just next to the board as it is or to show it as an overlay just when I create a task. The latter would even be way better for me because on my "small" FullHD screen I find it very uncomfortable to read the issues in that narrow column.

            +1!

            Brian Pratz added a comment - +1!

            This would be very welcome. This icon is sometimes shown, but more often it's not. The bookmarklet helps, but this functionality should be included within Jira itself.

            Deleted Account (Inactive) added a comment - This would be very welcome. This icon is sometimes shown, but more often it's not. The bookmarklet helps, but this functionality should be included within Jira itself.

            julian.engel2015260672 added a comment -

            Would be a great usability improvement!

            julian.engel2015260672 added a comment - Would be a great usability improvement!

            Jan Hebnes added a comment -

            +1

            Jan Hebnes added a comment - +1

            Ham Solo added a comment -

            Agree. This is a request I get all the time. Should be able to make the issue detail view larger. 

            Ham Solo added a comment - Agree. This is a request I get all the time. Should be able to make the issue detail view larger. 

            It's very confusing that this is not possible in work mode, please do make it!

            Martijn van de Donk added a comment - It's very confusing that this is not possible in work mode, please do make it!

            Anjali B. added a comment -

            yes!! this would be a really useful. Thanks and look forward to the update soon. 

            Anjali B. added a comment - yes!! this would be a really useful. Thanks and look forward to the update soon. 

            Would like to have this feature vey much!

            Yuri van Geffen added a comment - Would like to have this feature vey much!

            yes, this would be a very useful feature for us. Looking forward for it

            Albert Zemba added a comment - yes, this would be a very useful feature for us. Looking forward for it

            Not sure if I got this right but we are using Jira 7.1.7 and as far as I see there is no Work/Plan Mode anymore.
            Assuming the former Work-Mode is the new "Active Sprint" view and the former Plan-Mode is now the "Backlog" view.

            Nevertheless when using the Backlog view, I can't resize the Detail View. The icon is there (all maior browsers the same), also the tool tip but it's greyed out and obviously not usable.
            When using the "Active Sprint" view, the icon is completely missing.

            Christoph Körner added a comment - Not sure if I got this right but we are using Jira 7.1.7 and as far as I see there is no Work/Plan Mode anymore. Assuming the former Work-Mode is the new "Active Sprint" view and the former Plan-Mode is now the "Backlog" view. Nevertheless when using the Backlog view, I can't resize the Detail View. The icon is there (all maior browsers the same), also the tool tip but it's greyed out and obviously not usable. When using the "Active Sprint" view, the icon is completely missing.

            We can now edit any field in the detail view in Work mode, making the detail view in both Planning and Work mode nearly identical....except for this feature.

            Angell Tsang added a comment - We can now edit any field in the detail view in Work mode, making the detail view in both Planning and Work mode nearly identical....except for this feature.

            +1. @Karsten Silkenbäumer, could you share your GM script with us?

            Angell Tsang added a comment - +1. @Karsten Silkenbäumer, could you share your GM script with us?

            +1 ; users asking for this ergonomically useful feature.

            Remon van Gijn added a comment - +1 ; users asking for this ergonomically useful feature.

            Karsten Silkenbäumer added a comment - - edited

            Was able to place your script, @Rob Boerman, in a greasemonkey script so I don't have to manually click a bookmarklet - works well if used together with waitForKeyElements.

            There's just one glitch (either used as bookmarklet or greasemonkey): after the initial width has been set, when clicking the resize icon it jumps back to 400px. You have to go and grab it again to be able to resize.

            Karsten Silkenbäumer added a comment - - edited Was able to place your script, @Rob Boerman, in a greasemonkey script so I don't have to manually click a bookmarklet - works well if used together with waitForKeyElements . There's just one glitch (either used as bookmarklet or greasemonkey): after the initial width has been set, when clicking the resize icon it jumps back to 400px. You have to go and grab it again to be able to resize.

            +1 on this

            Qualcomm Support added a comment - +1 on this

            Awesome, Rob, works perfectly. Now Atlassian, if the Plan mode's resizing would just keep working (in my instance, clicking and dragging the handle doesn't work at all and if I close and reopen the detail view, the handle vanishes completely!), it would be great.

            Thomas Keller added a comment - Awesome, Rob, works perfectly. Now Atlassian, if the Plan mode's resizing would just keep working (in my instance, clicking and dragging the handle doesn't work at all and if I close and reopen the detail view, the handle vanishes completely!), it would be great.

            robboerman added a comment - - edited

            Here's a workaround that adds the resize functionality to the work mode. Create a bookmarklet with the following text:

            javascript: {
            var dragBar = document.getElementById("ghx-detail-head");
            var detailView = document.getElementById("ghx-detail-view");
            var headerGroup = document.getElementById("ghx-column-header-group");
            var controlGroup = document.getElementById("ghx-detail-head");
            var tmpElem = document.createElement('div');
            tmpElem.innerHTML = '<span style="display: block;" id="js-sizer" class="ghx-sizer ui-resizable-handle ui-resizable-w" data-tooltip="Resize Detail View" original-title=""><span class="ghx-icon ghx-icon-sizer"></span></span>';
            var dragElem = tmpElem.childNodes[0];
            controlGroup.insertBefore(dragElem,controlGroup.childNodes[0]);

            var currentWidth = localStorage.getItem('jiraWidth') || '400px';
            currentStylesheet = document.createElement('style');
            currentStylesheet.innerHTML = '#ghx-detail-view

            { width: ' + currentWidth + ' !important;}

            ';
            document.body.insertBefore(currentStylesheet, document.body.childNodes[0]);

            dragBar.addEventListener ("mousedown" , startJiraDrag , false);
            var stateMouseDown = false;
            var mouseStartX = 0;
            var jiraStartWidth, jiraHeaderWidth;
            var currentStylesheet;

            function startJiraDrag (ev) {
            if (currentStylesheet)

            { document.body.removeChild(currentStylesheet); }

            stateMouseDown = true;
            mouseStartX = ev.pageX;
            jiraStartWidth = detailView.clientWidth;
            jiraHeaderWidth = headerGroup.clientWidth;
            document.addEventListener ("mousemove" , continueJiraDrag , false);
            document.addEventListener ("mouseup" , endJiraDrag , false);
            }

            function continueJiraDrag (ev)

            { var pX = ev.pageX; detailView.style.width = (jiraStartWidth + mouseStartX - pX) + "px"; headerGroup.style.width = (jiraHeaderWidth - mouseStartX + pX) + "px"; }

            function endJiraDrag () {
            currentStylesheet = document.createElement('style');
            currentStylesheet.innerHTML = '#ghx-detail-view

            { width: ' + detailView.style.width + ' !important;}

            ';
            document.body.insertBefore(currentStylesheet, document.body.childNodes[0]);
            localStorage.setItem('jiraWidth',detailView.style.width);

            document.removeEventListener ("mousemove" , continueJiraDrag , false);
            document.removeEventListener ("mouseup" , endJiraDrag , false);
            }
            };void(0);

            Happy resizing

            robboerman added a comment - - edited Here's a workaround that adds the resize functionality to the work mode. Create a bookmarklet with the following text: javascript: { var dragBar = document.getElementById("ghx-detail-head"); var detailView = document.getElementById("ghx-detail-view"); var headerGroup = document.getElementById("ghx-column-header-group"); var controlGroup = document.getElementById("ghx-detail-head"); var tmpElem = document.createElement('div'); tmpElem.innerHTML = '<span style="display: block;" id="js-sizer" class="ghx-sizer ui-resizable-handle ui-resizable-w" data-tooltip="Resize Detail View" original-title=""><span class="ghx-icon ghx-icon-sizer"></span></span>'; var dragElem = tmpElem.childNodes [0] ; controlGroup.insertBefore(dragElem,controlGroup.childNodes [0] ); var currentWidth = localStorage.getItem('jiraWidth') || '400px'; currentStylesheet = document.createElement('style'); currentStylesheet.innerHTML = '#ghx-detail-view { width: ' + currentWidth + ' !important;} '; document.body.insertBefore(currentStylesheet, document.body.childNodes [0] ); dragBar.addEventListener ("mousedown" , startJiraDrag , false); var stateMouseDown = false; var mouseStartX = 0; var jiraStartWidth, jiraHeaderWidth; var currentStylesheet; function startJiraDrag (ev) { if (currentStylesheet) { document.body.removeChild(currentStylesheet); } stateMouseDown = true; mouseStartX = ev.pageX; jiraStartWidth = detailView.clientWidth; jiraHeaderWidth = headerGroup.clientWidth; document.addEventListener ("mousemove" , continueJiraDrag , false); document.addEventListener ("mouseup" , endJiraDrag , false); } function continueJiraDrag (ev) { var pX = ev.pageX; detailView.style.width = (jiraStartWidth + mouseStartX - pX) + "px"; headerGroup.style.width = (jiraHeaderWidth - mouseStartX + pX) + "px"; } function endJiraDrag () { currentStylesheet = document.createElement('style'); currentStylesheet.innerHTML = '#ghx-detail-view { width: ' + detailView.style.width + ' !important;} '; document.body.insertBefore(currentStylesheet, document.body.childNodes [0] ); localStorage.setItem('jiraWidth',detailView.style.width); document.removeEventListener ("mousemove" , continueJiraDrag , false); document.removeEventListener ("mouseup" , endJiraDrag , false); } };void(0); Happy resizing

            O added a comment -

            @Kevin Wennemuth: The +1 button is called "Vote for this issue". Please don't spam all watchers with comments which don't add anything useful.

            O added a comment - @Kevin Wennemuth: The +1 button is called "Vote for this issue". Please don't spam all watchers with comments which don't add anything useful.

            +1 on this

            Kevin Wennemuth added a comment - +1 on this

            I'd really love to see this implemented in work mode also

            deanhutchisonfuturenet added a comment - I'd really love to see this implemented in work mode also

            Resizing "Issue Detail View" in Plan mode already exists, please implement it in Work mode, also. This is very important for devs. Thanks.

            Ivan Petrovic added a comment - Resizing "Issue Detail View" in Plan mode already exists, please implement it in Work mode, also. This is very important for devs. Thanks.

            Here is a workaround for the problem. Create a bookmark in your browser with the following bookmarklet as text:

            javascript: {document.getElementById("ghx-pool-column").style.width="500px";};void(0);
            

            This sets the width of the left pane to 500px when you run the bookmarklet.

            Holger Oehm added a comment - Here is a workaround for the problem. Create a bookmark in your browser with the following bookmarklet as text: javascript: {document.getElementById( "ghx-pool-column" ).style.width= "500px" ;};void(0); This sets the width of the left pane to 500px when you run the bookmarklet.

            I don't know why this hasn't been prioritized. It already exists in Plan Mode, and provides an important/compelling way to get devs to interact more with Jira Agile, because it doesn't require opening the full ticket on it's own screen.

            Yet with the current fixed width, if a task contains subtasks (and most of ours do), and one actually cares as to e.g., time remaining in these subs, the user is forced to engage in an awkward left-to-right-to-left horizontal slider dance; and if you have more than 7-8 subtasks, you can't even do that, because the first few scroll vertically off the screen before you can even interact with the horizontal slider.

            Given that this has already been completed for Plan mode, one might presume that the effort for work mode (notwithstanding work-view specific issues) would be incremental

            Andrew Gansler added a comment - I don't know why this hasn't been prioritized. It already exists in Plan Mode, and provides an important/compelling way to get devs to interact more with Jira Agile, because it doesn't require opening the full ticket on it's own screen. Yet with the current fixed width, if a task contains subtasks (and most of ours do), and one actually cares as to e.g., time remaining in these subs, the user is forced to engage in an awkward left-to-right-to-left horizontal slider dance; and if you have more than 7-8 subtasks, you can't even do that, because the first few scroll vertically off the screen before you can even interact with the horizontal slider. Given that this has already been completed for Plan mode, one might presume that the effort for work mode (notwithstanding work-view specific issues) would be incremental

            Thanks, mjopson But what I actually meant was an option to turn off that the Detail View shows up when the issue-key or similar is clicked.

            In my view, the readability is too degraded in both columns and the Detail View to be useful in most cases.

            Frank Jensen added a comment - Thanks, mjopson But what I actually meant was an option to turn off that the Detail View shows up when the issue-key or similar is clicked. In my view, the readability is too degraded in both columns and the Detail View to be useful in most cases.

            frankern The Detail View can be closed using the x in the top right or the menu item in the Boards drop-down. It will only reopen if the menu item is used, the issue-key on a card is clicked or the keyboard shortcut 't' is used when a card is selected.

            Martin (Inactive) added a comment - frankern The Detail View can be closed using the x in the top right or the menu item in the Boards drop-down. It will only reopen if the menu item is used, the issue-key on a card is clicked or the keyboard shortcut 't' is used when a card is selected.

            We use many columns, and their issues get almost unreadable when the Detail View shows up on the right. Would be nice if it was an option to turn it off.

            Frank Jensen added a comment - We use many columns, and their issues get almost unreadable when the Detail View shows up on the right. Would be nice if it was an option to turn it off.

            I really love the agile boards within Jira, but I also like the new detail view within the issue search view of Jira. I like the list of issues on the left and the ticket details on the right.
            What about an option (not as default Warnung ) on the agile boards to only show the column of the marked ticket on the left and give the Detail View the remaining space on the right? Just like it is done with the issue search view. Or at least give it the size of two columns and loose one column in that view.
            I would not even have a big issue with loosing the Drag&Drop functionality between columns in this view. But it would give me a list view of my tasks, ordered according to my swimlanes, and the whole ticket with all features and functions on the right (including dropping files as attachment to the ticket).
            If I need to switch columns, I could then go back to the default view, or by any other smart option.

            Martin Hanke added a comment - I really love the agile boards within Jira, but I also like the new detail view within the issue search view of Jira. I like the list of issues on the left and the ticket details on the right. What about an option (not as default Warnung ) on the agile boards to only show the column of the marked ticket on the left and give the Detail View the remaining space on the right? Just like it is done with the issue search view. Or at least give it the size of two columns and loose one column in that view. I would not even have a big issue with loosing the Drag&Drop functionality between columns in this view. But it would give me a list view of my tasks, ordered according to my swimlanes, and the whole ticket with all features and functions on the right (including dropping files as attachment to the ticket). If I need to switch columns, I could then go back to the default view, or by any other smart option.

            We are only using kanban boards and that does not have a plan mode. We have a separate board for planning (which is a work board because of the kanban style).

            Wouter de Vaal added a comment - We are only using kanban boards and that does not have a plan mode. We have a separate board for planning (which is a work board because of the kanban style).

            Paul added a comment -

            Agree with with previous comment. The Detail View is the most important part of the screen! Our team runs our scrum calls for the "Work" tab and the cards on the left do not convey very much information. We need to be able to view the detailed information!

            Paul added a comment - Agree with with previous comment. The Detail View is the most important part of the screen! Our team runs our scrum calls for the "Work" tab and the cards on the left do not convey very much information. We need to be able to view the detailed information!

            When descriptions of issues contain a lot of text, it would be nice if the detail view could be resized in work mode. Columns can shrink until a minimum width. This minimum width does not have to be a width where the columns are still readable, but it has to provide a way to switch quickly between the scrum/kanban board view and a detailed description (or other information) of a certain issue.

            tjhkuijpers added a comment - When descriptions of issues contain a lot of text, it would be nice if the detail view could be resized in work mode. Columns can shrink until a minimum width. This minimum width does not have to be a width where the columns are still readable, but it has to provide a way to switch quickly between the scrum/kanban board view and a detailed description (or other information) of a certain issue.

              smikolajczuk Sylwia Mikołajczuk
              Anonymous Anonymous
              Votes:
              303 Vote for this issue
              Watchers:
              159 Start watching this issue

                Created:
                Updated:
                Resolved: