Issue Editor
- Janos Biro (Unlicensed)
- ChrisM (Unlicensed)
TRY Plangle on our Demo site without installing it in your environment !
How to switch to Plangle?
Our issue editor is clearly the central piece of our plugin that gives you
- a brand new hierarchical view with
- all your Epics, Stories and sub-tasks of your JIRA Agile Board
- JIRA Agile Quick Filter support
- 2 display mode for Epics
- Excel like navigation and editing capabilities with
- reordering Epics, Stories, sub-tasks (copy-paste and drag&drop)
- relocation of Stories and sub-tasks to other Epics and Stories (copy-paste and drag&drop)
- COMING SOON collapsing/expanding Stories and Epics
- Quick JIRA issue creation (Epics, Stories, Sub-tasks, and our Quick sub-tasks)
- supporting multi-project Boards
- supporting multi-project Boards
- Flexible estimation of Stories and sub-tasks
- the ability to set the issue type and Work Type of sub-tasks
Hierarchical view
With our hierarchical view you can look at all your Epics, Stories and sub-tasks of the selected JIRA Agile Board on the same page, in an Excel-like format - something that is just not possible in JIRA Agile.
The issues displayed in this view adhere to the settings of your JIRA Board (query filter).
You can find two different Epic display modes in Plangle, that correspond the 2 common Epic handling approaches in practice.
You can always switch between the two modes on the Configuration screen of Plangle.
Epics displayed/handled as Big Stories
In this mode we keep the order of the Epics, the Stories within Epics and the sub-tasks within Stories (we use the same Rank field as JIRA Agile).
You can not break an Epic to multiple parts in this mode, since we designed it for those who treat their Epics as Big Stories. Therefore we assume that you complete your Epics one after another.
Epics displayed/handled as Story groups (JIRA Agile style)
In this mode we keep the order of the Stories and the sub-tasks within Stories (we use the same Rank field as JIRA Agile), and display Epic as labels, just like JIRA Agile does.
Sprints, other filters
Would you like to filter for Sprints or for "Done" issues or just use a text filter?
Plangle is designed mainly for the initial planning process when you want to see all your Stories,
and for later occasions when you want to have a birds-eye-view on your project but yes, not a bad idea...
Let us know and we'll include the feature!
You can also vote for this feature directly here.
More columns
Would you like to see more columns to edit additional properties of Stories/Sub-tasks?
For initial planning purposes they seem more than enough, but let us know if you disagree!
You can also vote for this feature directly here.
Navigation and Editing
You can navigate within our table just like in any other Excel-like editors therefore...
| Action | Keyboard | Other | Comments |
|---|---|---|---|
| Navigate | Up-Down-Right-Left Tab, Shift-Tab PageUp, PageDown Home, End | Mouse movement | |
| Edit any given cell | Enter key, just start typing | Double click | |
| Insert new line | Insert | "+" icon at the beginning of the line Context menu | |
| Delete line | Delete | Trash bin icon at the end of the line Context menu | Deletes the whole issue hierarchy from that point |
| Copy-Paste | Ctrl+C, Ctrl+V | you can also try it with multiple fields | |
| Edit issue in JIRA dialog | Ctrl+E | you can even edit Quick Sub-tasks with it | |
| COMING SOON Collapse Stories/Epics | |||
Reordering of Epics, Stories, sub-tasks | Drag & Drop | ||
| Relocation of Stories and sub-tasks to other Epics and Stories | Drag & Drop |
Undo support
Would you like to use an Excel-like Undo feature?
Well, that is pretty hard, but let us know and we'll try to include the feature!
You can also vote for this feature directly here.
Issue creation/editing/deletion
How to create/edit/delete Epics/Stories/sub-tasks?
To create these types of issues just create a new line anywhere you want and insert the Summary of the Epic/Story/Subtask into the corresponding column.
If you want to create an issue with type other than the default "Story" please use the selector.
As soon as you leave the cell we'll create the issue for you in JIRA.
To delete an Epic/Story/Story just delete the corresponding line
Your user must have the "Delete Issues" JIRA permission (by default only JIRA Administrators have it, ask your JIRA Administrator to allow you to delete issues)
or just press "Delete"
To edit an Epic/Story/Story just edit the given cell, we'll save any changes as soon as you leave the cell.
How to create/edit/delete Quick sub-tasks?
Quick Subtasks
Quick sub-tasks is our marvelous invention to create sub-tasks for Stories only specifying the estimations for them, their name will be derived from the Story's name and a configurable prefix.
Their type can also be pre-configured.
Learn more about Quick sub-tasks.
To create Quick sub-tasks just enter a valid estimation into to corresponding column in the row of the parent Story.
As soon as you leave the cell we'll create the sub-task for the Story in JIRA giving it a name, issue type and Work Type according to your configuration.
To delete a Quick Subtask delete the estimation from the corresponding cell.
Your user must have the "Delete Issues" JIRA permission (by default only JIRA Administrators have it)
To edit a Quick Subtask just edit the given cell, we'll save any changes as soon as you leave the cell.
Editing estimation
Epics
You can't edit it, however we'll calculate it for you adding up the estimations of the Stories within.
Stories
Just go to the line of the Story and edit the corresponding cell.
OR you can just click on the "Copy estimation" button to make the estimation of all to Stories equal to the sum of the estimation of its sub-tasks
OR you can use our context menu to make the estimation of the given Story equal to the sum of the estimation of its sub-tasks
or 
Field for Story estimation
Please note that we respect the settings of your JIRA Agile Board, so will use the very field to store the Story estimation as JIRA Agile
Set Story estimation to the sum of its subtasks' remaining estimation
Well, we are considering the possibility to introduce this feature (requested and refused e.g. here GHS-7719) despite the fact that it is against all we believe in.
But we are servants of real world requirements so let us know and we'll include the feature!
You can also vote for this feature directly here.
Sub-tasks
Just go to the line of the Sub-task and edit the corresponding cell.
If you can enter estimation...
Please note that we respect the settings of your JIRA Agile Board ("Time tracking"), so will not let you estimate sub-tasks if it is switched off.
Quick sub-tasks
Quick sub-tasks are represented in Plangle as their estimation (a number only) therefore editing its estimation is the same as editing the Quick Subtask itself.
If you can not edit Quick Subtasks...
Please note that we respect the settings of your JIRA Agile Board ("Time tracking"), so will not let you estimate quick sub-tasks if it is switched off.
Multi-project Boards
In case of multi-project boards we allow you to specify the project you would like to create your issue in while always offering a sensible default.
Editing issue type and Work Type
PM Type
Work Type (Project Management Type) is our saying to "type of work" like "Frontend Development", "Backend development", "QA", etc. usually stored in a single-choice JIRA custom field.
Learn more about Work Types.
Sub-tasks
You can edit the issue type and Work Type of your sub-tasks using the context menu (right click on the field of the Subtask)
Quick sub-tasks
The Work Type of Quick sub-tasks is controlled in the Configuration
Editing other JIRA fields of issues
Currently we only support editing the "Description" field of Epics/Stories/sub-tasks.
For initial planning purposes they seem more than enough, but let us know if you disagree!
