@Dark Dev - Very cool, although my work's security team probably would worry about me installing it for our production Jira.
A few questions:
Can we see the code? (Yes, I guess I could poke around in the Chrome install directory, but I meant like in a Github repo)
Can Atlassian use your code? :-D
I can't figure out how to get to the Config options.
The resizeable, and movable pop-up window is very cool. Kind of makes you wonder why Atlassian didn't implement their modal that way. But ... can you please implement keyboard shortcuts J and K to go next and back?
For curious but cautious folks, here's a screenshot of how @Dark Dev 's extension (also, your name might also cause concern for my security team) turns the Modal into something more useful. The "Quick view" window can be resized and moved whereever you want. And that size and position is remembered.
Oh, I'm dumb. Figured out how to get to the Configuration options. Click on it:
Whaaaa, look at all these OPTIONS:
Ok, another feature request. If we select side panel, can you make it resizeable > than 50% by using the slider. Your side panel seems to lock at whatever percentage we choose in the config panel.
While this is fun to play with, a slider would probably be a bit more convenient:
@Darryl Lee - you mean the in Jira splitter slider, right? FYI - if you pin the extension (via the pin icon) and in the settings panel (2nd tab) select the "Extension icon popup" option then you can quickly click that icon and instantly drag the side panel easily:
@Darryl Lee - To get back to some of your questions:
I can look at implementing shortcut keys for easier navigation of the list (J + K). I figured I'd get the extension out sooner rather than later to get some feedback on the needs of the users actually wanting to use this (instead of the methods forced on us at the moment). I initially did consider adding keyboard shortcut support BUT decided against since I did not want to negatively impact folks who already leverage those in their existing workflows. I might need to add that behind a user-configurable keybinding so as to not intercept (and swallow) key events and prevent a feature that users of Jira would already expect to work in a certain manner.
Can we see the code? I'll be sure to upload it to github in the future - not done this yet but was already in the cards for a later point in time.
Can Atlassian use your code? I'm not opposed to them taking what I have and using it. That said: they're in a much better spot than me since I'm leveraging their code/accessibility hooks/framework to accomplish what I'm doing. There would be no need for them to do that since it is their code to begin with.
Not sure I'm fully following what you are talking about regarding the slider locking the viewport. The "Force side panel" config slider value will be remembered and applied whenever the current Jira Preview Panel is displayed. This allows users to set the Preview Panel to something more than 50% (the max that is allowed using the current implementation delivered by Atlassian). So if you want the Preview Panel to take say 80% of the viewport size then just set that "Force side panel" slider value to 80%.
Ohey @Dark Dev to my first three questions, cool cool cool.
(Well, the third one was kind of a joke. I just want Atlassian to fix this in any way possible and if it made it easier to look at how you did it, that'd be great.)
Re: the last one - Atlassian's implementation of the Side Panel is that it is resizeable via the slider, but it maxes out at 50%. @Marc Muhlestein was the first person to suggest that if Atlassian simply "allow[ed us] to make the side bar window bigger and stretch further across the screen." that would probably address a good chunk of the complaints about this change.
Your extension lets you set the size of the Preview panel to an exact size, but only via your extension Configuration panel (which I made a video of, because seeing it in real-time is fun). Once you've set it to 80%, then you cannot adjust the size within the Jira UI with the slider.
Ah ok now that I look at @Sean Brewington's CSS hack I see it also "locked" the size. Is there no way to intercept/override Atlassian's code that limits sizing to 50%?
@Darryl Lee - I initially went down that road to try to override Atlassian's max slider rules within their UI itself (basically to remove the clamp rule they have in their resizer UI element). I decided against trying to fight their implementation since I would need to explicitly "disable" some very targeted UI elements and if they decided to change it in the future then my extension would just cease to work as expected. Due to this reason I kept all my hooks leveraging their internal accessibility identifiers (what I assume they use for their automation testing efforts OR accessibility tools) which means the extension should continue to work as long as their accessibility identifiers are not changed (at least that is the hope since it would be a major undertaking on their side to update all their testing tools).
That said: I could possibly explore some kind of "experimental" tab / feature set where this configuration could exist and be enabled. I'd need to think on this some.
157 comments