Currently JIRA Client shows the Issues like in MS Outlook view (Tree, preview & details). It will be convenient to have a EXCEL kind of tabular view wherein the Editor can work with several issues simultaneously, do edit/copy & paste, view several issues in one window etc. In real life scenario apart from Bugs, there are cases where different issues are somehow interlinked with eachother. So such a tabular view for editing will be of good value to the users.
Igor Sereda
July 10, 2006
Am I getting this right - you are suggesting to have in JIRA Client tabbed panels, each holding one issue to allow simultaneous editing? Or did I miss the idea? (Can't see how Excel is relevant here except that it also has tabs.)
Last EAP release of JIRA Client does not yet allow to edit issues. We're working on editing right now. Our current idea is to implement editing as it is done in Deskzilla - in a separate window for each issue.
Also, JIRA Client has tabbed query results. Right clicking on a tab shows a menu where "Clone Tab" action may be selected to duplicate current tab with state. That may be also helpful.
Best regards,
Igor
Let me explain with the problem I am trying to solve. I am trying to model Requirements using JIRA. In our company, the process is such that the Requirements are broken down into Sub-features and Sub-features in turn into a set of code impacts.
So, the relationship is something like 1 Requirement contains 'n' sub-features which in turn contains 'm' code impacts.
I am modelling Requirement, Sub-features & Code impacts with different issue types in JIRA. So to implement 1 requirement, m+n issues have to be resolved.
With this kind of modelling, all m+n issues are interrelated. Currently, this process is implemented in EXCEL. Designers are used to copy/paste things & do EXCEL Autofilter to filter out similar issues to view/edit them. EXCEL view greatly enhances the viewing experience of many issues with one screen/view. A casual look at a set of rows puts the designer in context.
Such a view in JIRA client will give the Designers the same comfort level of Quick edit and copy/paste as a single EXCEL sheet. I hope its clear now.
Igor Sereda
July 10, 2006
Yeah, it's clear now, thanks. If, for example, JIRA Client is be able to display a requirement and all its sub-features and code impacts in a "tree table" - a hierarchy with columns for all fields, then I guess that would look similar to what you get in EXCEL.
Though we don't have excel-like autofilter (a cool idea to consider), it would be possible to filter issues with sub-queries.
By the way, in the process you have described, if a designer edits an issue in EXCEL, how does it get uploaded to JIRA? Isn't data lost occasionally?
We are introducing JIRA only now. There was only EXCEL based working before. What we are trying to do now is to generate a JELLY Script out of EXCEL contents (using VB Macros in XLS) and run the script in JIRA to import the issues from EXCEL.
To modify existing issues in JIRA, one has to export data from JIRA (via Issue Navigator->XLS export), modify in XLS and again generate the Jelly script. Recently discovered difficulty: I am missing predefined Jelly tags for modifying issues(:- I have to code my own Jelly tags to modify issues. Thats when I got interested in your JIRA client as it looked like a more professional solution to solve many other problems. For example, the offline Issue access is one such critical feature I liked. Without this, I can't imagine working with my Laptop at home on JIRA issues.
It would be nice to have the issue view have the columns you choose be editable.
E.g.
You have the Priority field in the view. You should be able to click and have a drop down of priorities appear and be able to select them.
Also it would be nice to select N issues and edit them all as you can do with the Bulk Edit feature in JIRA web client.
E.g.
Select N issues and set their priority.
And for my third post in a row!
With the awesome table view you have it makes me want to use the JIRA client to triage bugs. But with no bulk edit of multiple issue / inline editing it is really not friendly to triaging lots of bugs.
Check out these links for where people have requested functionality in JIRA. If the JIRA Client could do this then people will buy the client just for triaging!! :-)
http://jira.atlassian.com/browse/JRA-7133 Allow issue editing in the issue navigator
http://jira.atlassian.com/browse/JRA-9457 Bulk Edit + per-bug edit ability
A user made a first pass at an edit inline tool for jira:
http://confluence.atlassian.com/display/JI...or+bug+triagers
Igor Sereda
December 4, 2006
msew,
Thanks a lot for your comments and links! We'll work on the in-grid editing and bulk edit in the next versions.
There are relevant issues in our issue database, you can add yourself to CC list to keep track on them:
http://bugzilla.almworks.com/show_bug.cgi?id=113
http://bugzilla.almworks.com/show_bug.cgi?id=179
Best regards,
Igor
Great!
Soon as those are pretty certain a number of sales will be coming your way :-)
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please
click here.