192 KiB
192 KiB
| 1 | issuekey | title | description | storypoint |
|---|---|---|---|---|
| 2 | GHS-1271 | As a JIRA Administrator I would like to be able to change the trigger of the night service | NULL | 5 |
| 3 | JSW-1271 | As a JIRA Administrator I would like to be able to change the trigger of the night service | NULL | 5 |
| 4 | GHS-1681 | Generic webwork aliases may clash with other plugins | Some web work actions have commands that have very generic aliases, such as "Update", "Move" and "Synch" etc. These aliases have a good chance to clash with the action name or aliases used by other plugins. These aliases should be given a name specific to the plugin, such as "UpdateGreenHopperDropBoard"... Alternatively, the bang syntax can be used in place of command aliases, such as "DropBoardAction!update". In this case, there is no need to define aliases for commands. (However, still need to define alias as an empty String; otherwise, a NPE will be thrown when parsing the xml.) | 5 |
| 5 | JSW-1681 | Generic webwork aliases may clash with other plugins | Some web work actions have commands that have very generic aliases, such as "Update", "Move" and "Synch" etc. These aliases have a good chance to clash with the action name or aliases used by other plugins. These aliases should be given a name specific to the plugin, such as "UpdateGreenHopperDropBoard"... Alternatively, the bang syntax can be used in place of command aliases, such as "DropBoardAction!update". In this case, there is no need to define aliases for commands. (However, still need to define alias as an empty String; otherwise, a NPE will be thrown when parsing the xml.) | 5 |
| 6 | GHS-1819 | Add text to the Agile Gadget "Invalid Project" message | When the error is "Invalid Project" add details that the project is not configured for use with GreenHopper - "Invalid Project - [Not configured for use with GreenHopper|http://confluence.atlassian.com/display/GH/Configuring+your+GreenHopper+Global+Settings#ConfiguringyourGreenHopperGlobalSettings-context]" | 2 |
| 7 | JSW-1819 | Add text to the Agile Gadget "Invalid Project" message | When the error is "Invalid Project" add details that the project is not configured for use with GreenHopper - "Invalid Project - [Not configured for use with GreenHopper|http://confluence.atlassian.com/display/GH/Configuring+your+GreenHopper+Global+Settings#ConfiguringyourGreenHopperGlobalSettings-context]" | 2 |
| 8 | GHS-1882 | Greenhopper ranking field is not displayed correctly if using Confluence Jira Issues macro | When using Greenhopper ranking field in conjunction with the jiraissues macro, the actual database field value is being reported in xml rather than a sanitized version. | 20 |
| 9 | JSW-1882 | Greenhopper ranking field is not displayed correctly if using Confluence Jira Issues macro | When using Greenhopper ranking field in conjunction with the jiraissues macro, the actual database field value is being reported in xml rather than a sanitized version. | 20 |
| 10 | GHS-2047 | Version can be set in the create issue screen in JIRA, but not in GreenHopper | Costumer has a project in which some users don't have schedule permission which means that they cannot manage the project backlog. However, they need the ability to raise new defects inside a specific version, e.g. when testing that sprint/version. They can do this via the JIRA create new issue screen. But they cannot do this via the GreenHopper user interface (when using the button "New card", the version is fixed as "Unscheduled"). In this case, the user should have the ability to set the version in both JIRA (create issue) and GreenHopper (new card) screens. | 5 |
| 11 | JSW-2047 | Version can be set in the create issue screen in JIRA, but not in GreenHopper | Costumer has a project in which some users don't have schedule permission which means that they cannot manage the project backlog. However, they need the ability to raise new defects inside a specific version, e.g. when testing that sprint/version. They can do this via the JIRA create new issue screen. But they cannot do this via the GreenHopper user interface (when using the button "New card", the version is fixed as "Unscheduled"). In this case, the user should have the ability to set the version in both JIRA (create issue) and GreenHopper (new card) screens. | 5 |
| 12 | GHS-2478 | As a user I would like the ability to see a horizontal swimlane on my Rapid Board | COS: - Based on Issue Priority Blocker - Only show swimlane when necessary - Warning if swimlane exceeds max amount - JQL longer term ---- In order to implement Kanban concepts like service class, etc. we need to be able to create horizontal swimlanes with limited WIP for each. For example, I might want to have: - Standard (Limit of 6) - Expedite (Limit of 1) - Fixed Delivery Date (Limit of 2) LeanKit Kanban has this feature (actually, it is far more advanced than what I am describing). | 13 |
| 13 | JSW-2478 | As a user I would like the ability to see a horizontal swimlane on my Rapid Board | COS: - Based on Issue Priority Blocker - Only show swimlane when necessary - Warning if swimlane exceeds max amount - JQL longer term ---- In order to implement Kanban concepts like service class, etc. we need to be able to create horizontal swimlanes with limited WIP for each. For example, I might want to have: - Standard (Limit of 6) - Expedite (Limit of 1) - Fixed Delivery Date (Limit of 2) LeanKit Kanban has this feature (actually, it is far more advanced than what I am describing). | 13 |
| 14 | JSW-2785 | As a GH user I would like to be able to view the cumulative flow diagram using story points | NULL | 13 |
| 15 | GHS-2863 | GreenHopper appends Project IDs to URL when adding to list of Enabled Projects, causes HTTP 413 error. | Per ticket here: https://support.atlassian.com/browse/GHS-2112 When adding select projects to the "Allowed Projects" listing (under Administration > GreenHopper > Enabled Projects,) adding a project to the allowed list creates a request URL like this: http://localhost:8080/secure//secure/SetAdmissibleProjects.jspa?decorator=none&listValue=10010%2C10000%2C Where the response is a "302 Temporarily Moved," a POST content size of zero, and a listValue entry that keeps getting longer. Eventually, the list gets so long that the page will not load due to an "HTTP 413 - Request entity too large" error. (Screenshots + Dev console in Chrome attached.) | 3 |
| 16 | JSW-2863 | GreenHopper appends Project IDs to URL when adding to list of Enabled Projects, causes HTTP 413 error. | Per ticket here: https://support.atlassian.com/browse/GHS-2112 When adding select projects to the "Allowed Projects" listing (under Administration > GreenHopper > Enabled Projects,) adding a project to the allowed list creates a request URL like this: http://localhost:8080/secure//secure/SetAdmissibleProjects.jspa?decorator=none&listValue=10010%2C10000%2C Where the response is a "302 Temporarily Moved," a POST content size of zero, and a listValue entry that keeps getting longer. Eventually, the list gets so long that the page will not load due to an "HTTP 413 - Request entity too large" error. (Screenshots + Dev console in Chrome attached.) | 3 |
| 17 | GHS-2881 | Investigate: Log work operation of a task in the task board redirect the page to "ALL Assignee". | *Steps to reproduce:* 1. Click on Agile Tab 2. Navigate to Chart Board > Task Board > Choose Assignee 3. This will display all cards for which the user is the Assignee 4. Log Work *Expected Result:* The work is succesfully logged The card should make the Assignee unchanged (that is maintaining same Assignee) *Actual Result:* work logged successfully The card is set to All Assignee | 2 |
| 18 | JSW-2881 | Investigate: Log work operation of a task in the task board redirect the page to "ALL Assignee". | *Steps to reproduce:* 1. Click on Agile Tab 2. Navigate to Chart Board > Task Board > Choose Assignee 3. This will display all cards for which the user is the Assignee 4. Log Work *Expected Result:* The work is succesfully logged The card should make the Assignee unchanged (that is maintaining same Assignee) *Actual Result:* work logged successfully The card is set to All Assignee | 2 |
| 19 | GHS-2882 | Changing the fixVersion of a card to a fixVersion outside the Parent results in a page refresh and a change of the fixVersion filter (unexpected and inconsistent behaviour) | From https://studio.atlassian.com/browse/JST-3848 {quote} This bug appeared on 14.2.2010, after the update on 13.2.2010. Go to Task Board, select version X and developer D. Change the version of a task to version Y. The filter changes to version Y and no developer is selected (filter to All Assignees). Was working fine until at least 11.2.2010, where the behaviour was that the flter stayed in place an a little message said something that "you can't view the message you were working on because it is not in the filter". The current behavior is really annoying because you have to get back to the version you were working on. Using the planning board is not an option because you cannot filter on the developer. {quote} | 5 |
| 20 | JSW-2882 | Changing the fixVersion of a card to a fixVersion outside the Parent results in a page refresh and a change of the fixVersion filter (unexpected and inconsistent behaviour) | From https://studio.atlassian.com/browse/JST-3848 {quote} This bug appeared on 14.2.2010, after the update on 13.2.2010. Go to Task Board, select version X and developer D. Change the version of a task to version Y. The filter changes to version Y and no developer is selected (filter to All Assignees). Was working fine until at least 11.2.2010, where the behaviour was that the flter stayed in place an a little message said something that "you can't view the message you were working on because it is not in the filter". The current behavior is really annoying because you have to get back to the version you were working on. Using the planning board is not an option because you cannot filter on the developer. {quote} | 5 |
| 21 | GHS-2912 | As a user I would like to be able to quickly toggle the display of columns on and off on A Board, similar to the quick filter buttons | NULL | 8 |
| 22 | JSW-2912 | As a user I would like to be able to quickly toggle the display of columns on and off on A Board, similar to the quick filter buttons | NULL | 8 |
| 23 | GHS-2915 | When creating a new card with security level on the card, it does not have 'None' in the select for security level. | NULL | 2 |
| 24 | JSW-2915 | When creating a new card with security level on the card, it does not have 'None' in the select for security level. | NULL | 2 |
| 25 | GHS-2919 | As a GH User I would like the Assignee and Reporter fields on the New Card dialog to be the new shiny autocomplete to improve performance | NULL | 5 |
| 26 | JSW-2919 | As a GH User I would like the Assignee and Reporter fields on the New Card dialog to be the new shiny autocomplete to improve performance | NULL | 5 |
| 27 | GHS-2923 | WorklogHistoryCacheImpl doesn't remove cache registration on disposal | From [JST-4291|https://studio.atlassian.com/browse/JST-4291?focusedCommentId=39798&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-39798] It's not possible to disable and re-enable the GH plugin in UPM atm. The problem is that the _com.atlassian.greenhopper.service.timetracking.WorklogHistoryCacheImpl_ doesn't clean up its registered cache on disposal. It should implement _org.springframework.beans.factory.DisposableBean_ and call _cacheManager.removeCache(CACHE_NAME)_ (watch out for ISE) or check for _net.sf.ehcache.CacheManager.cacheExists(String)_ on _afterPropertiesSet_. | 2 |
| 28 | JSW-2923 | WorklogHistoryCacheImpl doesn't remove cache registration on disposal | From [JST-4291|https://studio.atlassian.com/browse/JST-4291?focusedCommentId=39798&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-39798] It's not possible to disable and re-enable the GH plugin in UPM atm. The problem is that the _com.atlassian.greenhopper.service.timetracking.WorklogHistoryCacheImpl_ doesn't clean up its registered cache on disposal. It should implement _org.springframework.beans.factory.DisposableBean_ and call _cacheManager.removeCache(CACHE_NAME)_ (watch out for ISE) or check for _net.sf.ehcache.CacheManager.cacheExists(String)_ on _afterPropertiesSet_. | 2 |
| 29 | GHS-2987 | As a user I would like the ability to edit the remaining estimate without using the JIRA Log Work dialog | Acceptance Criteria: - Clicking on the Remaining Estimate field will allow inline edit - Similar behaviour to the new inline text edit behaviour | 8 |
| 30 | JSW-2987 | As a user I would like the ability to edit the remaining estimate without using the JIRA Log Work dialog | Acceptance Criteria: - Clicking on the Remaining Estimate field will allow inline edit - Similar behaviour to the new inline text edit behaviour | 8 |
| 31 | GHS-2989 | Ability to print on standard index cards | We are in the process of migrating from another system to Jira. We currently using a bubblejet printer to print stories directly onto 3x5 index cards. With the current Greenhopper printing functionality, we can't print one card per page and therefore can't print directly onto cards. We would like the ability print one card per page with the card layout sized to fit well on a 3x5 index card | 2 |
| 32 | JSW-2989 | Ability to print on standard index cards | We are in the process of migrating from another system to Jira. We currently using a bubblejet printer to print stories directly onto 3x5 index cards. With the current Greenhopper printing functionality, we can't print one card per page and therefore can't print directly onto cards. We would like the ability print one card per page with the card layout sized to fit well on a 3x5 index card | 2 |
| 33 | GHS-2994 | As a user I would like the Days Remaining Gadget to cascade down and select a release date that does exist, even if it is within a child version | For instance, at present it selects the parent version which has no release date set (cause we don't yet know when we release). Instead, it should select the child version that has a release date. | 3 |
| 34 | JSW-2994 | As a user I would like the Days Remaining Gadget to cascade down and select a release date that does exist, even if it is within a child version | For instance, at present it selects the parent version which has no release date set (cause we don't yet know when we release). Instead, it should select the child version that has a release date. | 3 |
| 35 | GHS-2998 | As a user I would like the Rapid Board to be available via Labs | COS: - Labs option under General Configuration to enable/disable the Rapid Board - Rapid Board displayed in Agile drop down when enabled - Feedback button (using Andreas' JIRA plugin) in the header - Manage option when on Rapid Board for current RV | 5 |
| 36 | JSW-2998 | As a user I would like the Rapid Board to be available via Labs | COS: - Labs option under General Configuration to enable/disable the Rapid Board - Rapid Board displayed in Agile drop down when enabled - Feedback button (using Andreas' JIRA plugin) in the header - Manage option when on Rapid Board for current RV | 5 |
| 37 | GHS-3003 | As a user I would like the past three comments (space permitting) on an issue to be displayed in the detailed card view on the rapid board | COS: - link to Show next 5 comments (if more than n left) - link to Show all remaining comments (if any left) - details of total number of comments - v1 to have no tools (∞ + edit), no index, no twixy - expanded by default) | 5 |
| 38 | JSW-3003 | As a user I would like the past three comments (space permitting) on an issue to be displayed in the detailed card view on the rapid board | COS: - link to Show next 5 comments (if more than n left) - link to Show all remaining comments (if any left) - details of total number of comments - v1 to have no tools (∞ + edit), no index, no twixy - expanded by default) | 5 |
| 39 | GHS-3006 | As a rapid board user I would like to return to my last viewed Rapid View when I click on the Agile tab | COS - If I am a Rapid Board user and have a remembered Rapid View (from my last visit) then I would like to be taken to that when I click on Agile, instead of being taken to the Planning Board | 5 |
| 40 | JSW-3006 | As a rapid board user I would like to return to my last viewed Rapid View when I click on the Agile tab | COS - If I am a Rapid Board user and have a remembered Rapid View (from my last visit) then I would like to be taken to that when I click on Agile, instead of being taken to the Planning Board | 5 |
| 41 | GHS-3011 | As a user i would like the ability to manage my rapid views similar to jira managed filters | List all rapid views, link to edit, delete. View option for non-owners. | 5 |
| 42 | JSW-3011 | As a user i would like the ability to manage my rapid views similar to jira managed filters | List all rapid views, link to edit, delete. View option for non-owners. | 5 |
| 43 | GHS-3017 | Configuration of custom and scrum templates lost after upgrade | If custom templates were created or the scrum template was modified in a version prior to 5.4.2, an upgrade to one of the affected ones will cause the configuration associated with these templates to be lost. This bug is caused as a side effect of fixing http://jira.atlassian.com/browse/GHS-2826. See http://confluence.atlassian.com/x/fBIaDg for additional information. | 5 |
| 44 | JSW-3017 | Configuration of custom and scrum templates lost after upgrade | If custom templates were created or the scrum template was modified in a version prior to 5.4.2, an upgrade to one of the affected ones will cause the configuration associated with these templates to be lost. This bug is caused as a side effect of fixing http://jira.atlassian.com/browse/GHS-2826. See http://confluence.atlassian.com/x/fBIaDg for additional information. | 5 |
| 45 | GHS-3020 | Editing the labels triggers a page reload - on PlanningBoard | NULL | 2 |
| 46 | JSW-3020 | Editing the labels triggers a page reload - on PlanningBoard | NULL | 2 |
| 47 | GHS-3029 | As a user I would like the ability to create and release a fix version containing all of the issues in my done column | COS: - Based on correct permissions (Project Administrator) - Release button on RHS column (normally "Done") - Release dialog w/ - new versions - name the fix version - set the description - set the release date (auto populate with today's date, plus date picker) - Notifications that explain what occured | 8 |
| 48 | JSW-3029 | As a user I would like the ability to create and release a fix version containing all of the issues in my done column | COS: - Based on correct permissions (Project Administrator) - Release button on RHS column (normally "Done") - Release dialog w/ - new versions - name the fix version - set the description - set the release date (auto populate with today's date, plus date picker) - Notifications that explain what occured | 8 |
| 49 | GHS-3030 | As a user I would like the ability to add maximum and minimum constraints to a column on my Rapid View based upon total issue count | COS - Configure this on the Manage Rapid View using inline edit - Default to total issue count (include sub tasks, exclude swimlane duplicates) - Yellow for min constraint busted in header - Red for max constraint busted in header - Show min, current, max at top of column | 5 |
| 50 | JSW-3030 | As a user I would like the ability to add maximum and minimum constraints to a column on my Rapid View based upon total issue count | COS - Configure this on the Manage Rapid View using inline edit - Default to total issue count (include sub tasks, exclude swimlane duplicates) - Yellow for min constraint busted in header - Red for max constraint busted in header - Show min, current, max at top of column | 5 |
| 51 | GHS-3050 | As a user I would like to be able to edit a Rapid View that I created using someone elses saved filter | COS: - regardless of who owns the Saved Filter, if I have created a Rapid View based on it I can edit the Rapid View - Other users can not edit my Rapid View - Manage Rapid View has message saying you cant configure and link to owner | 5 |
| 52 | JSW-3050 | As a user I would like to be able to edit a Rapid View that I created using someone elses saved filter | COS: - regardless of who owns the Saved Filter, if I have created a Rapid View based on it I can edit the Rapid View - Other users can not edit my Rapid View - Manage Rapid View has message saying you cant configure and link to owner | 5 |
| 53 | GHS-3065 | As a user I would like a control chart showing the time an issue was in progress | COS - in progress is defined as those columns which are yellow | 8 |
| 54 | JSW-3065 | As a user I would like a control chart showing the time an issue was in progress | COS - in progress is defined as those columns which are yellow | 8 |
| 55 | GHS-3066 | As a user I would like the ability to configure the "expedite" swimlane on my Rapid View | COS - Change the name of the swimlane, default to 'Expedite' - one swimlane with JQL "AND" - configure by JQL in a free text field - configure on the Manage Rapid View page - no validation, no autocomplete - if there is no JQL the swimlane is not displayed | 5 |
| 56 | JSW-3066 | As a user I would like the ability to configure the "expedite" swimlane on my Rapid View | COS - Change the name of the swimlane, default to 'Expedite' - one swimlane with JQL "AND" - configure by JQL in a free text field - configure on the Manage Rapid View page - no validation, no autocomplete - if there is no JQL the swimlane is not displayed | 5 |
| 57 | GHS-3070 | Issues without a priority set should not be given a priority icon on the Rapid Board as it is misleading/incorrect | 1 | |
| 58 | JSW-3070 | Issues without a priority set should not be given a priority icon on the Rapid Board as it is misleading/incorrect | 1 | |
| 59 | GHS-3093 | As a user I would like to see a cumulative flow diagram on my Rapid Board to show the progression of issues across my board | COS: - In Flot - On the Reporting tab of the Rapid Board - Based upon the current Rapid View - Similar colour scheme to the gadget (for consistency) - Not configurable based on columns - Go to Control Chart when loading Reporting, have a drop down for chart types where 'Cumulative Flow Diagram' can be found | 8 |
| 60 | JSW-3093 | As a user I would like to see a cumulative flow diagram on my Rapid Board to show the progression of issues across my board | COS: - In Flot - On the Reporting tab of the Rapid Board - Based upon the current Rapid View - Similar colour scheme to the gadget (for consistency) - Not configurable based on columns - Go to Control Chart when loading Reporting, have a drop down for chart types where 'Cumulative Flow Diagram' can be found | 8 |
| 61 | GHS-3097 | As a user I would like to be able to return an unlimited number of results | COS: - the query should be limited to the number of issues in Global Configuration, Query Results Limit - if there is no limit set it will return all issues | 3 |
| 62 | JSW-3097 | As a user I would like to be able to return an unlimited number of results | COS: - the query should be limited to the number of issues in Global Configuration, Query Results Limit - if there is no limit set it will return all issues | 3 |
| 63 | GHS-3099 | As a user I would like to see the mean and the standard deviation on my control chart | COS: - perhaps a similar style to http://people.iola.dk/olau/flot/examples/percentiles.html - show this as a line on the control chart for the mean, with a highlight to show std dev - no interaction expected - use all chart data - one standard deviation for the highlight | 3 |
| 64 | JSW-3099 | As a user I would like to see the mean and the standard deviation on my control chart | COS: - perhaps a similar style to http://people.iola.dk/olau/flot/examples/percentiles.html - show this as a line on the control chart for the mean, with a highlight to show std dev - no interaction expected - use all chart data - one standard deviation for the highlight | 3 |
| 65 | GHS-3104 | As a user I would like my everything else swimlane to exclude the issues from the configured swimlane | COS: - remove the card stubs in everything else - everything else swimlane appends swimlane JQL as "AND NOT" - remove unnecessary code (CSS and JS) - change 'default swimlane' to 'Everything Else' | 3 |
| 66 | JSW-3104 | As a user I would like my everything else swimlane to exclude the issues from the configured swimlane | COS: - remove the card stubs in everything else - everything else swimlane appends swimlane JQL as "AND NOT" - remove unnecessary code (CSS and JS) - change 'default swimlane' to 'Everything Else' | 3 |
| 67 | GHS-3106 | As a user I would like the 'New Column' text in a new column to be selected enabling quick update | 1 | |
| 68 | JSW-3106 | As a user I would like the 'New Column' text in a new column to be selected enabling quick update | 1 | |
| 69 | GHS-3107 | As a user I would like the global statuses to be sorted by name in the Manage Rapid View to assist me when creating a new column | Unmapped column only | 2 |
| 70 | JSW-3107 | As a user I would like the global statuses to be sorted by name in the Manage Rapid View to assist me when creating a new column | Unmapped column only | 2 |
| 71 | GHS-3108 | As a user I would like a link from my Manage Rapid View screen back to the Rapid Board | 1 | |
| 72 | JSW-3108 | As a user I would like a link from my Manage Rapid View screen back to the Rapid Board | 1 | |
| 73 | GHS-3110 | GreenHopper does not display the assignee auto-complete when the "User Searching by Full Name" JIRA configuration option has been turned off | See [JST-4804|https://studio.atlassian.com/browse/JST-4804] for more information. Please resolve that when resolving this. | 3 |
| 74 | JSW-3110 | GreenHopper does not display the assignee auto-complete when the "User Searching by Full Name" JIRA configuration option has been turned off | See [JST-4804|https://studio.atlassian.com/browse/JST-4804] for more information. Please resolve that when resolving this. | 3 |
| 75 | GHS-3132 | URL doesn't select issue on the Planning Board as it should | For [instance|https://jira.atlassian.com/secure/ProjectBoard.jspa?pageType=PlanningBoard&selectedProjectId=12200&viewIssueKey=GHS-1098&subType=ProjectBoard#] on GreenHopper 5.6.3 that does not select the correct page and the issue on the correct page. | 3 |
| 76 | JSW-3132 | URL doesn't select issue on the Planning Board as it should | For [instance|https://jira.atlassian.com/secure/ProjectBoard.jspa?pageType=PlanningBoard&selectedProjectId=12200&viewIssueKey=GHS-1098&subType=ProjectBoard#] on GreenHopper 5.6.3 that does not select the correct page and the issue on the correct page. | 3 |
| 77 | GHS-3146 | As a user I would like to be able to add another swimlane to my Rapid View | COS: - Add additional swimlanes - Ability to delete swimlanes - Not Sortable (will be another story) - JIRA Restful Table UI/UX e.g. Manage Versions | 5 |
| 78 | JSW-3146 | As a user I would like to be able to add another swimlane to my Rapid View | COS: - Add additional swimlanes - Ability to delete swimlanes - Not Sortable (will be another story) - JIRA Restful Table UI/UX e.g. Manage Versions | 5 |
| 79 | GHS-3161 | When clicking on issue on control chart show issue in detail view | 1 | |
| 80 | JSW-3161 | When clicking on issue on control chart show issue in detail view | 1 | |
| 81 | JSW-3772 | As a rapid board owner I would like to be able to have a column constraint for "Issues, excluding Sub-Tasks" | (!) Testing Notes (!) Q: What happens in the case with an issue that has a subtask not captured by the filter? A: (/) Nothing - the count is for parent issues and not sub-tasks, so the count will not be affected. Q: Test to see this works with Stories Swimlane config, as well as Queries. A: (/) Still works, though it is less clear what the issue count refers to given that you do not see the parent issue in the column it is in. Q: What about negative numbers? A: (/) They continue to not be allowed - same input controls for constraints as before. Q: Is this customizable for individual constraints, or globally for all constraints? A: (/) For the whole board, not individual columns Q: What if the last parent is removed from that column but it's subtasks remain? A: (/) The count drops to zero. Q: What happens if there is no subtask issuetype? A: (/) Nothing - the count should not be affected by issues which do not exist Q: What happens when there are quick filters active that filter out parent issues? What happens when there are quick filters active that filter out sub-task issues? A: (/) The count should still display the appropriate number of issues - so if column constraint excludes sub tasks then filtering out parents should set all visible counts to 0. | 2 |
| 82 | JSW-3993 | As a user, if I accidentally browse the Rapid Start before logout, I want to be about to go straight to RapidBoard when I login | Currently GreenHopper will remember that you were at the RapidStart when you logout, and when you log back in, clicking the Agile tab brings you back there. We want to change the behavior so that the user returns to the RapidBoard instead. This will reduce annoyance for the customer. | 2 |
| 83 | GHS-4171 | make sub projects | We really need this feature, where a single projects can have its own projects | 2 |
| 84 | JSW-4171 | make sub projects | We really need this feature, where a single projects can have its own projects | 2 |
| 85 | JSW-4478 | As a user, I would like to get visual feedback on the progress of Plan Mode's loading | When you have a lot of issues, it can be slow to load and it looks like nothing is happening. | 2 |
| 86 | JSW-4503 | As a user, I would like to be able to quickly filter issues out in Plan mode | Quick filters Best Effort is fine for now, probably same as quick filters on Work tab (seems consistent) The marker should still count items above the line even if they are filtered | 8 |
| 87 | GHS-4520 | As a user, I would like to just see Rapid Board everywhere Rapid View exists currently | NULL | 1 |
| 88 | JSW-4520 | As a user, I would like to just see Rapid Board everywhere Rapid View exists currently | NULL | 1 |
| 89 | GHS-4521 | In Doco: I would like to see Rapid Board everywhere Rapid View is currently | NULL | 1 |
| 90 | JSW-4521 | In Doco: I would like to see Rapid Board everywhere Rapid View is currently | NULL | 1 |
| 91 | JSW-4547 | As an OnDemand user, I'd like to be able to provide the Atlassian team with feedback on GH labs features | Need to implement a "got feedback" mechanism for OnDemand like we do in BTF. | 2 |
| 92 | JSW-4559 | A problem with Rapid Board`s cards display. | If a Rapid Board includes many columns (> 11 columns)and a screen resolution is resolution - 1280 x 720, then ticket`s key and summary are become unreadable (like on an attached screenshot). !rapid_board.png|thumbnail! This becomes problem where user cannot use less amount of columns and we can`t increase a browser window size in some cases (when using a laptop, for example). Thanks in advance. SAC ticket: https://support.atlassian.com/browse/GHS-3831 | 2 |
| 93 | GHS-4633 | New features in dashboard for drop down list | New features in dashboard for drop down list a drop down list should be added to the dashboard for easy access | 3 |
| 94 | JSW-4633 | New features in dashboard for drop down list | New features in dashboard for drop down list a drop down list should be added to the dashboard for easy access | 3 |
| 95 | JSW-4655 | As a user, I would like to view attachments when elaborating stories in a Sprint planning meeting | - Also present in work mode - Image gallery view as in JIRA if possible | 8 |
| 96 | GHS-4657 | As a user, I'd like to see a burn down that includes both the 'feeling' of the burndown as well as the actual facts | NULL | 8 |
| 97 | JSW-4657 | As a user, I'd like to see a burn down that includes both the 'feeling' of the burndown as well as the actual facts | NULL | 8 |
| 98 | JSW-4659 | As a user, I would like to see the issue priority in plan mode | Need some basic design | 2 |
| 99 | JSW-4662 | As a user, I would like sub tasks to have the same Sprint as their parent in all cases | - For now force all subtasks to be complete on a complete Story before allowing Sprint to be finished | 5 |
| 100 | GHS-4679 | NullPointerException occurs when editing issue - related to 'GreenHopper Released Version History' field | When attempting to edit an issue in JIRA the edit fails when user clicks the 'update' button, it throws a java.lang.NullPointerException at the top of the edit issue window. If you check the logs the following error appears: {noformat} @400000004f45c7530fe9a96c 2012-02-23 01:57:45,265 TP-Processor10 ERROR sysadmin 117x11680x1 evyd4p 59.167.133.99,207.223.247.46 /secure/QuickEditIssue.jspa [jira.bc.issue.DefaultIssueService] Exception occurred editing issue: java.lang.NullPointerException @400000004f45c7530fe9b13c java.lang.NullPointerException @400000004f45c7530fe9b524 at java.util.AbstractCollection.addAll(AbstractCollection.java:303) @400000004f45c7530fe9b524 at com.pyxis.greenhopper.jira.customfields.ReleasedVersionHistoryCFType.updateValue(ReleasedVersionHistoryCFType.java:68) @400000004f45c7530fed04cc at com.pyxis.greenhopper.jira.customfields.ReleasedVersionHistoryCFType.updateValue(ReleasedVersionHistoryCFType.java:25) @400000004f45c7530fed08b4 at com.atlassian.jira.issue.fields.CustomFieldImpl.updateValue(CustomFieldImpl.java:405) @400000004f45c7530fed08b4 at com.atlassian.jira.issue.fields.CustomFieldImpl.updateValue(CustomFieldImpl.java:366) @400000004f45c7530fed146c at com.atlassian.jira.issue.managers.DefaultIssueManager.updateFieldValues(DefaultIssueManager.java:589) @400000004f45c7530fed146c at com.atlassian.jira.issue.managers.DefaultIssueManager.updateIssue(DefaultIssueManager.java:554) @400000004f45c7530fed1854 at com.atlassian.jira.bc.issue.DefaultIssueService.update(DefaultIssueService.java:272) @400000004f45c7530fed27f4 at com.atlassian.jira.bc.issue.DefaultIssueService.update(DefaultIssueService.java:246) @400000004f45c7530fed2bdc at sun.reflect.GeneratedMethodAccessor1929.invoke(Unknown Source) @400000004f45c7530fed2bdc at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) @400000004f45c7530fed2fc4 at java.lang.reflect.Method.invoke(Method.java:597) @400000004f45c7530fed33ac at com.atlassian.multitenant.impl.MultiTenantComponentFactoryImpl$AbstractMultiTenantAwareInvocationHandler.invokeInternal(MultiTenantComponentFactoryImpl.java:181) @400000004f45c7530fed3794 at com.atlassian.multitenant.impl.MultiTenantComponentFactoryImpl$MultiTenantAwareInvocationHandler.invoke(MultiTenantComponentFactoryImpl.java:211) @400000004f45c7530fed3b7c at $Proxy298.update(Unknown Source) @400000004f45c7530fed3b7c at sun.reflect.GeneratedMethodAccessor1929.invoke(Unknown Source) @400000004f45c7530fed434c at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) @400000004f45c7530fed434c at java.lang.reflect.Method.invoke(Method.java:597) @400000004f45c7530fed4734 at com.atlassian.plugin.osgi.hostcomponents.impl.DefaultComponentRegistrar$ContextClassLoaderSettingInvocationHandler.invoke(DefaultComponentRegistrar.java:129) @400000004f45c7530fed4f04 at $Proxy298.update(Unknown Source) @400000004f45c7530fed52ec at sun.reflect.GeneratedMethodAccessor1929.invoke(Unknown Source) @400000004f45c7530fed52ec at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) @400000004f45c7530fed56d4 at java.lang.reflect.Method.invoke(Method.java:597) @400000004f45c7530fed5abc at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:154) @400000004f45c7530fed5ea4 at $Proxy298.update(Unknown Source) @400000004f45c7530fed5ea4 at com.atlassian.jira.quickedit.action.QuickEditIssue.doExecute(QuickEditIssue.java:128) @400000004f45c7530fed628c at webwork.action.ActionSupport.execute(ActionSupport.java:165) @400000004f45c7530fed79fc at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:82) @400000004f45c7530fed79fc at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39) @400000004f45c7530fed7de4 at webwork.interceptor.NestedInterceptorChain.proceed(NestedInterceptorChain.java:31) @400000004f45c7530fed7de4 at webwork.interceptor.ChainedInterceptor.intercept(ChainedInterceptor.java:16) @400000004f45c7530fed85b4 at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:35) @400000004f45c7530fed916c at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:205) @400000004f45c7530fed916c at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:143) @400000004f45c7530fed9554 at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:152) @400000004f45c7530fed993c at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) @400000004f45c7530fed9d24 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) @400000004f45c7530feda10c at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) @400000004f45c7530feda10c at com.atlassian.jira.web.filters.steps.ChainedFilterStepRunner.doFilter(ChainedFilterStepRunner.java:78) @400000004f45c7530feda4f4 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) @400000004f45c7530feda8dc at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) @400000004f45c7530fedacc4 at com.atlassian.core.filters.HeaderSanitisingFilter.doFilter(HeaderSanitisingFilter.java:44) @400000004f45c7530fedacc4 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) @400000004f45c7530fedb87c at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) @400000004f45c7530fedb87c at com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:46) @400000004f45c7530fedbc64 at com.atlassian.plugin.servlet.filter.DelegatingPluginFilter$1.doFilter(DelegatingPluginFilter.java:66) @400000004f45c7530fedbc64 at com.atlassian.applinks.core.rest.context.ContextFilter.doFilter(ContextFilter.java:25) @400000004f45c7530fedc81c at com.atlassian.plugin.servlet.filter.DelegatingPluginFilter.doFilter(DelegatingPluginFilter.java:74) @400000004f45c7530fedc81c at com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:42) @400000004f45c7530fedcc04 at com.atlassian.plugin.servlet.filter.DelegatingPluginFilter$1.doFilter(DelegatingPluginFilter.java:66) @400000004f45c7530fedcc04 at com.atlassian.agmp.integration.jira.ReprovisionConfigFilter.doFilter(ReprovisionConfigFilter.java:87) @400000004f45c7530fedd3d4 at com.atlassian.plugin.servlet.filter.DelegatingPluginFilter.doFilter(DelegatingPluginFilter.java:74) {noformat} I've confirmed that this error is only occuring for issues which have a value in a custom field of type 'GreenHopper Released Version History'. h2. Workaround This only appears to occur when the 'Release Version History' field has been added to the screen used for editing. If you remove this field from all screens then the issue should be resolved. | 2 |
| 101 | JSW-4679 | NullPointerException occurs when editing issue - related to 'GreenHopper Released Version History' field | When attempting to edit an issue in JIRA the edit fails when user clicks the 'update' button, it throws a java.lang.NullPointerException at the top of the edit issue window. If you check the logs the following error appears: {noformat} @400000004f45c7530fe9a96c 2012-02-23 01:57:45,265 TP-Processor10 ERROR sysadmin 117x11680x1 evyd4p 59.167.133.99,207.223.247.46 /secure/QuickEditIssue.jspa [jira.bc.issue.DefaultIssueService] Exception occurred editing issue: java.lang.NullPointerException @400000004f45c7530fe9b13c java.lang.NullPointerException @400000004f45c7530fe9b524 at java.util.AbstractCollection.addAll(AbstractCollection.java:303) @400000004f45c7530fe9b524 at com.pyxis.greenhopper.jira.customfields.ReleasedVersionHistoryCFType.updateValue(ReleasedVersionHistoryCFType.java:68) @400000004f45c7530fed04cc at com.pyxis.greenhopper.jira.customfields.ReleasedVersionHistoryCFType.updateValue(ReleasedVersionHistoryCFType.java:25) @400000004f45c7530fed08b4 at com.atlassian.jira.issue.fields.CustomFieldImpl.updateValue(CustomFieldImpl.java:405) @400000004f45c7530fed08b4 at com.atlassian.jira.issue.fields.CustomFieldImpl.updateValue(CustomFieldImpl.java:366) @400000004f45c7530fed146c at com.atlassian.jira.issue.managers.DefaultIssueManager.updateFieldValues(DefaultIssueManager.java:589) @400000004f45c7530fed146c at com.atlassian.jira.issue.managers.DefaultIssueManager.updateIssue(DefaultIssueManager.java:554) @400000004f45c7530fed1854 at com.atlassian.jira.bc.issue.DefaultIssueService.update(DefaultIssueService.java:272) @400000004f45c7530fed27f4 at com.atlassian.jira.bc.issue.DefaultIssueService.update(DefaultIssueService.java:246) @400000004f45c7530fed2bdc at sun.reflect.GeneratedMethodAccessor1929.invoke(Unknown Source) @400000004f45c7530fed2bdc at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) @400000004f45c7530fed2fc4 at java.lang.reflect.Method.invoke(Method.java:597) @400000004f45c7530fed33ac at com.atlassian.multitenant.impl.MultiTenantComponentFactoryImpl$AbstractMultiTenantAwareInvocationHandler.invokeInternal(MultiTenantComponentFactoryImpl.java:181) @400000004f45c7530fed3794 at com.atlassian.multitenant.impl.MultiTenantComponentFactoryImpl$MultiTenantAwareInvocationHandler.invoke(MultiTenantComponentFactoryImpl.java:211) @400000004f45c7530fed3b7c at $Proxy298.update(Unknown Source) @400000004f45c7530fed3b7c at sun.reflect.GeneratedMethodAccessor1929.invoke(Unknown Source) @400000004f45c7530fed434c at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) @400000004f45c7530fed434c at java.lang.reflect.Method.invoke(Method.java:597) @400000004f45c7530fed4734 at com.atlassian.plugin.osgi.hostcomponents.impl.DefaultComponentRegistrar$ContextClassLoaderSettingInvocationHandler.invoke(DefaultComponentRegistrar.java:129) @400000004f45c7530fed4f04 at $Proxy298.update(Unknown Source) @400000004f45c7530fed52ec at sun.reflect.GeneratedMethodAccessor1929.invoke(Unknown Source) @400000004f45c7530fed52ec at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) @400000004f45c7530fed56d4 at java.lang.reflect.Method.invoke(Method.java:597) @400000004f45c7530fed5abc at com.atlassian.plugin.osgi.bridge.external.HostComponentFactoryBean$DynamicServiceInvocationHandler.invoke(HostComponentFactoryBean.java:154) @400000004f45c7530fed5ea4 at $Proxy298.update(Unknown Source) @400000004f45c7530fed5ea4 at com.atlassian.jira.quickedit.action.QuickEditIssue.doExecute(QuickEditIssue.java:128) @400000004f45c7530fed628c at webwork.action.ActionSupport.execute(ActionSupport.java:165) @400000004f45c7530fed79fc at com.atlassian.jira.action.JiraActionSupport.execute(JiraActionSupport.java:82) @400000004f45c7530fed79fc at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:39) @400000004f45c7530fed7de4 at webwork.interceptor.NestedInterceptorChain.proceed(NestedInterceptorChain.java:31) @400000004f45c7530fed7de4 at webwork.interceptor.ChainedInterceptor.intercept(ChainedInterceptor.java:16) @400000004f45c7530fed85b4 at webwork.interceptor.DefaultInterceptorChain.proceed(DefaultInterceptorChain.java:35) @400000004f45c7530fed916c at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:205) @400000004f45c7530fed916c at webwork.dispatcher.GenericDispatcher.executeAction(GenericDispatcher.java:143) @400000004f45c7530fed9554 at com.atlassian.jira.web.dispatcher.JiraWebworkActionDispatcher.service(JiraWebworkActionDispatcher.java:152) @400000004f45c7530fed993c at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) @400000004f45c7530fed9d24 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) @400000004f45c7530feda10c at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) @400000004f45c7530feda10c at com.atlassian.jira.web.filters.steps.ChainedFilterStepRunner.doFilter(ChainedFilterStepRunner.java:78) @400000004f45c7530feda4f4 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) @400000004f45c7530feda8dc at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) @400000004f45c7530fedacc4 at com.atlassian.core.filters.HeaderSanitisingFilter.doFilter(HeaderSanitisingFilter.java:44) @400000004f45c7530fedacc4 at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235) @400000004f45c7530fedb87c at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) @400000004f45c7530fedb87c at com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:46) @400000004f45c7530fedbc64 at com.atlassian.plugin.servlet.filter.DelegatingPluginFilter$1.doFilter(DelegatingPluginFilter.java:66) @400000004f45c7530fedbc64 at com.atlassian.applinks.core.rest.context.ContextFilter.doFilter(ContextFilter.java:25) @400000004f45c7530fedc81c at com.atlassian.plugin.servlet.filter.DelegatingPluginFilter.doFilter(DelegatingPluginFilter.java:74) @400000004f45c7530fedc81c at com.atlassian.plugin.servlet.filter.IteratingFilterChain.doFilter(IteratingFilterChain.java:42) @400000004f45c7530fedcc04 at com.atlassian.plugin.servlet.filter.DelegatingPluginFilter$1.doFilter(DelegatingPluginFilter.java:66) @400000004f45c7530fedcc04 at com.atlassian.agmp.integration.jira.ReprovisionConfigFilter.doFilter(ReprovisionConfigFilter.java:87) @400000004f45c7530fedd3d4 at com.atlassian.plugin.servlet.filter.DelegatingPluginFilter.doFilter(DelegatingPluginFilter.java:74) {noformat} I've confirmed that this error is only occuring for issues which have a value in a custom field of type 'GreenHopper Released Version History'. h2. Workaround This only appears to occur when the 'Release Version History' field has been added to the screen used for editing. If you remove this field from all screens then the issue should be resolved. | 2 |
| 102 | GHS-4710 | As an admin who hasn't seen the analytics question I would like to be asked on every page until I say yes or no | Remove the X Getting Started, Rapid Board, Configure Rapid Board, Manage Rapid Board, GreenHopper General Configuration page, License Page | 5 |
| 103 | JSW-4710 | As an admin who hasn't seen the analytics question I would like to be asked on every page until I say yes or no | Remove the X Getting Started, Rapid Board, Configure Rapid Board, Manage Rapid Board, GreenHopper General Configuration page, License Page | 5 |
| 104 | JSW-4711 | As a user, I'd like the issue I just created on a board to be the selected issue by default, or to get a popup indicating it was created if the issue is not visible | To be clear: * Create issue and it is visible -> select the issue * Create issue and it is not visible -> show a popup * Does not happen in Report mode (only Plan and Work) | 2 |
| 105 | JSW-4734 | As a user, I would like to see the issue count on the Sprint marker | NULL | 5 |
| 106 | JSW-4765 | MVR: Issue operation to jump to a rapid board from an Issue | This is a complex one, so let's break it down. * Providing an issue operation for an Issue to be able to "go to" a Rapid Board for this issue. * The boards available to go to will be calculated only once the user initiates the action. * Valid boards are calculated based on which boards the user has permission to see, as well as if the issue matches the filter of the board; ** In the case of Kanban boards, the issue must also match the Work mode sub filter. It should *not* match if the issue only appears on Report mode. ** In the case of Scrum boards, the issue may appear in any mode (Plan, Work or Report). * If there are no valid boards, the user will be shown a message; ** _Optionally, the user will be prompted to create a new board based on the project of the issue_. * If there are multiple valid boards, the user will be prompted to choose one. * If there is only one valid board, or if the user has chosen a board, the user will be redirected instantly. * The user will be redirected to the precise location of the issue on the chosen board. ** The issue will be selected if the location is Plan or Work mode. ** In the case of a Scrum board, if the location is the Report mode, and the issue belongs to more than one sprint, the most recent sprint's retrospective report will be chosen. | 8 |
| 107 | JSW-4766 | MVR: Report page showing Sprints (with a selector), include table of issues, link to issue nav | NULL | 8 |
| 108 | JSW-4767 | MVR: Sprint Report to include a burndown for the Sprint itself | - Smaller one than in the general one - Hovers if possible | 8 |
| 109 | JSW-4768 | MVR: Make the burndown chart understand when an issue was added/removed from Sprint (i.e understand scope change) | - Should handle change of Story Points value https://extranet.atlassian.com/display/GHDEV/Estimation+and+Tracking+in+the+Rapid+Board#EstimationandTrackingintheRapidBoard-Tracking - The graph begins at the start time of the Sprint, it logically ends on the specified end date of the Sprint (which is marked on the graph) but continues until the time the Sprint was actually closed - Allow the Sprint to be specified but default to currently active Sprint - The start value of the graph does not compensate for changes after the start of the sprint to the value - Items burn down as they reach the done column - Items that are added to the Sprint after its beginning are shown as scope change - Items that are removed from the Sprint after its beginning are shown as scope change - Items that have their estimate changed after the beginning of the Sprint are shown as scope change - Scope changes (i.e anything other than a burndown) are shown with some sort of visual signal and information on hovering the inflection point | 13 |
| 110 | JSW-4772 | MVR: Search (filter) for Rapid Board Plan mode - (Search by issue key or by summary text) | Client side as a first attempt Straight direct match of substring is minimum (no need for multiple keywords) | 13 |
| 111 | JSW-4773 | MVR: Add a cog to access issue actions from detail view | NULL | 5 |
| 112 | GHS-4774 | MVR: Allow plan mode to show subtasks, include a default filter for Scrum boards which hide subtasks | NULL | 13 |
| 113 | JSW-4774 | MVR: Allow plan mode to show subtasks, include a default filter for Scrum boards which hide subtasks | NULL | 13 |
| 114 | JSW-4775 | MVR: Implement issue swimlane strategy | Java remodelling | 20 |
| 115 | JSW-4776 | MVR: Implement visualisation of swimlanes as parents | Needs drop down in the config (refer to design) Parents always present except if themselves and all of their children are filtered Swimlane configuration retains user defined filters even if you switch to parent strategy | 13 |
| 116 | JSW-4792 | As a user, I would like to see the status of an issue in the detail view (in work and plan) | Not including the Status icon as this may be 'gone' in JIRA soon anyway... | 2 |
| 117 | JSW-4794 | As a user I would like to rank above the marker even when there is one issue in scope | NULL | 2 |
| 118 | JSW-4812 | MVR: Prompt the user to resolve the parent when the subtasks are all done | Just for parent swimlane strategy | 8 |
| 119 | JSW-4813 | MVR: Prompt at the end of a Sprint if unfinished parent stories with all complete subtasks exist | - Offer to continue or to cancel - Note to the user that they will go back to the backlog - List of issues | 5 |
| 120 | JSW-4862 | MV?: When all of the subtasks of a story are complete but the parent is not show an affordance that can be clicked by the user to advance the parent (and try to resolve the issue) | Clarification: Summary states that the affordance only needs to appear when the parent status is out of sync. Should the affordance just show the status of the parent Minimum required | 5 |
| 121 | JSW-4863 | MV?: Implement the skinny detail view | Moves as you traverse with n and p Fixed on RHS with all columns visible) (was Shifts to the right of the currently selected column | 20 |
| 122 | JSW-4864 | As a user I would like to go to GH as my default JIRa home page | This story involves implementing Trevs MyHome page feature. Currently this is a per user dark feature. We could add a -button- affordance to make this available on the board page | 1 |
| 123 | JSW-4877 | Upgrade task to unify Board/Sprint data into AO instead of using PropertySets | NULL | 5 |
| 124 | JSW-4888 | MVR: Agile issue web panel to display Scrum information of an issue | This is a complex one, so let's break it down. * Providing a web panel on the View Issue page to display Scrum information. * Information displayed will be a list of the sprints of which this issue is a part of. * The sprints will be broken down into two sections: Active and Completed * Sprints will provide a link to "go to the sprint". This means going to a Rapid Board for this sprint. * The boards available to go to will be calculated only once the user initiates the action. * Valid boards are calculated based on which boards the user has permission to see, as well as if the issue matches the filter of the board; ** Only scrum boards will be considered. * If there are no valid boards, the user will be shown a message; * If there are multiple valid boards, the user will be prompted to choose one. * If there is only one valid board, or if the user has chosen a board, the user will be redirected instantly. * The user will be redirected to the precise location of the sprint on the chosen board; ** If the sprint is active, the location is Work mode of the board. ** If the sprint is completed, the location is the retrospective report of that sprint on that board. | 8 |
| 125 | JSW-4906 | As a user, I'd like to avoid confusion when hitting enter in the description field and having that save by saving on blur | NULL | 2 |
| 126 | JSW-4910 | Enhance Sprint Report | - Include scheduled start/end and actual end (triggered when hit complete button) - Divide into issues completed during Sprint and those not, include the status of the item at the end of the Sprint - Include the estimate statistic for each item (ideally from time the item was added to the Sprint but current if not easy) - include the sum of the statistic (i.e the velocity) - -Call out issues that were added and removed- | 8 |
| 127 | JSW-4911 | Implement Sprint Burndown chart (for Numeric Fields) | - For the specified estimation statistic field (assuming the 'time tracking' option has not been specified for tracking) | 5 |
| 128 | JSW-4913 | Make the Sprint Burndown chart use remaining estimate when the board has been configured that way | - Changes in the remaining estimate are burned down as they happen - Time spent burns up - Items that are added to the Sprint after its beginning are shown as scope change - Items that are removed from the Sprint after its beginning are shown as scope change | 20 |
| 129 | JSW-4914 | Add a subtasks tab to the detail view on plan mode | - Add a new 'Subtasks' tab with an add button - For each sub task: Show summary, key, avatar, status, remaining estimate, edit button (JIRA Edit Dialog), delete button | 8 |
| 130 | JSW-4915 | Allow the backlog item estimation statistic to be selected as any numeric field in the issue | - Allow the Backlog item estimation statistic for a *Scrum* Rapid Board to be selected, the default should be the Story Point field but it should also be possible to set any other Numeric field - Show the Backlog item estimation statistic on the Plan mode in the lozenge - Replaces existing use of lozenge (in detail view & card view) - Label unit as 'Estimate', on hover show unit | 13 |
| 131 | JSW-4916 | Implement the Velocity chart | - The Velocity chart will show amount of the Backlog item estimation statistic from Sprint to Sprint - The graph is bucketed by Sprint - For each Sprint the velocity is equal to the sum of the backlog item estimate for all issues that are in the last column at the end of the Sprint - Would also show the sum of estimation statistic committed to during the Sprint (i.e the ones that did not get done) - The PBI estimate used is from the time the issue was added to the Sprint (i.e at the start of the Sprint if the item was in at Sprint start or at the time it was added in the middle of the Sprint) - The graph is followed by a table that describes the values shown in the table - For each Sprint a row is shown along with the sum of completed and non completed PBIs, hyperlink to the Sprint report - A link is provided to the detailed Sprint burndown for that Sprint - For now hardcode to last 7 | 8 |
| 132 | JSW-4919 | Allow the Backlog item estimation statistic for a Rapid Board to be set to Original Estimate | Allow the Backlog item estimation statistic for a Rapid Board to be selected to be set to Original Estimate | 13 |
| 133 | JSW-4920 | Warn on start sprint if primary items do not have the backlog item estimate set | - Warn offers OK or Cancel - "The following issues do not have a <estimate unit> estimate specified. Estimates applied following the start of the Sprint will be considered scope change" - Happens before the Sprint name and dates dialog | 5 |
| 134 | GHS-4922 | Allow a numeric field to be specified Sprint tracking statistic for the Rapid Board | - Show the statistic in detail, editable in plan mode only - If a Sprint is started warn if there is no estimate for an item that has the sprint tracking statistic | 8 |
| 135 | JSW-4922 | Allow a numeric field to be specified Sprint tracking statistic for the Rapid Board | - Show the statistic in detail, editable in plan mode only - If a Sprint is started warn if there is no estimate for an item that has the sprint tracking statistic | 8 |
| 136 | JSW-4966 | Add a detail view cog menu item to remove an issue from a Sprint (DOES cause scope change) | - Work mode only - Confirmation dialog - Notification that it was successfully removed (with a link to the issue on Plan mode) | 5 |
| 137 | JSW-4967 | Implement Data Table for Burndown chart | - The graph is followed by a table that describes the exact timeline shown in the graph: * At each point in time the issue that changed and the values that changed are shown * At time 0 the table lists all issues that were present at the beginning of the graph * At time <end> the table lists all issues that were remaining | 3 |
| 138 | JSW-4970 | Go to best Sprint in retro report | - If the Sprint Retro report is opened and I've not opened it before I should go latest finished Sprint - If I was on the 'latest finished sprint' when I go back to the retro report it should always show me the 'latest finished sprint' | 3 |
| 139 | JSW-4971 | Implement Original Estimate burndown | NULL | 8 |
| 140 | JSW-4972 | Allow a user to configure tracking to use Remaining Estimate | - In configuration describe this as "This option will show the Remaining Estimate on the detail view so you can edit it" - Make card and detail view operate as expected - If the estimate statistic is set to "Original Time Estimate", then when you enter an Estimate for the first time, it should also update the Remaining Time Estimate for the issue *iff* there is no value set for it already. | 20 |
| 141 | JSW-5004 | Make TEAMCAL integration work | NULL | 3 |
| 142 | JSW-5011 | Incoporate the changes to My JIRA home into GH next | The JIRA team have tweaked (changed) the My JIRA home in 5.1 Martin Meinhold 12:53:07 the link element in the web-item only contains the target url, like: <link linkId="set_my_jira_home_issuenav">/secure/IssueNavigator.jspa</link> The actual update url is provided by JIRA itself so no: /secure/MyJiraHome!Set.jspa?target= 12:54:01 So we need to put in 2 web items (since its not on 5.0.x) and have a condition on them so that only one turns up as appropriate. | 1 |
| 143 | JSW-5039 | As a user, following Sprint completion I'd like to see the report of everything that happened automatically | NULL | 1 |
| 144 | GHS-5069 | Figure out what to do with issues which come into a sprint with no statistic value and then change half way through | - Put all items in to the data table at the bottom (i.e when they're added or removed from the Sprint) even if they do not have an estimate and therefore don't affect the burndown Add issue to sprint with no estimate, then change estimate, only shows as statistic value change in table. This problem is particularly bad when you then later remove the issue from the sprint - as the issue addition and removal is completely hidden from the table and is not shown as scope change. | 8 |
| 145 | JSW-5069 | Figure out what to do with issues which come into a sprint with no statistic value and then change half way through | - Put all items in to the data table at the bottom (i.e when they're added or removed from the Sprint) even if they do not have an estimate and therefore don't affect the burndown Add issue to sprint with no estimate, then change estimate, only shows as statistic value change in table. This problem is particularly bad when you then later remove the issue from the sprint - as the issue addition and removal is completely hidden from the table and is not shown as scope change. | 8 |
| 146 | JSW-5072 | As a planner I want to be able to show the sum of all issues' remaining estimate in an upcoming sprint | As a RapidBoardUser I want to be able to show the sum of all issues remainingestimate, so I can see which workload I have. COS: - Not show if equal - Only when tracking is enabled for a board | 5 |
| 147 | JSW-5077 | As an admin I would like to know what greenhopper upgrade tasks are up to | Currently GH does some things to protect itself in upgrade tasks but not enough We need to track * when a upgrade tasks runs * what upgrade task * what version of GH at the time | 3 |
| 148 | JSW-5085 | Rearrange the Agile menu | - Labs configuration option used to enable new Agile menu - 5 most recently used boards at the top, 'Other...' takes you to manage - 'Classic...' at the bottom, takes me to Planning version board initially then I can choose another one using the dropdown menu - Click on Agile should work as currently (i.e most recent classic or Rapid Board) | 8 |
| 149 | JSW-5087 | MVR: When I click 'Classic...' in the new menu structure give me a way back | - If I go to Classic I need a notification saying I probably don't want to be here and a link to go back to the Getting Started page - This message always appears until I say don't show again - Shaun will write the copy - Only with new menu structure "The Classic boards are no longer being actively improved and are not recommended for use in new projects.{0}Learn more about {1}Getting Started{2} with the new boards." | 5 |
| 150 | JSW-5089 | MVR: Change keyboard shortcuts (Go to Planning Board) etc based on the new Agile menu structure | - Make 'g' and 'h' - Go to Agile - Make 'g' and 'a' - Go to Agile - Invisible - Make 'g' and 't' - Go to Agile - Invisible | 5 |
| 151 | JSW-5090 | MVR: Rename issue operations (or remove not used ones) when new Agile menu structure is enabled | - Remove: Go to Planning/Task - Rename 'Rapid Board' to 'Agile Board' | 2 |
| 152 | GHS-5094 | Translate URLs according to new terminology | NULL | 8 |
| 153 | JSW-5094 | Translate URLs according to new terminology | NULL | 8 |
| 154 | JSW-5106 | When starting a Sprint with Time Remaining set to the Sprint tracking statistic, warn if Remaining Estimate is unset (or uninherited from children) for any item | NULL | 3 |
| 155 | JSW-5107 | As a rapid board user with buggy browser extensions, I don't want exceptions thrown from extensions to break GreenHopper | GreenHopper appears to use a global exception handler that reacts to any uncaught exception by showing an error on the rapid board. We've seen a couple of support requests from users with browser extensions that throw exceptions. In some cases, the errors may be benign and GreenHopper could continue to function normally, but the errors alarm people, and as a result they raise support requests. This could potentially be caused by any JavaScript that runs within the context of the page: browser extensions, GreaseMonkey scripts, even JIRA plugins or Speakeasy extensions. | 5 |
| 156 | JSW-5115 | Remove Scrum Rapid Board from labs | - Always on, remove labs checkbox - Update Getting Started screen (should still include some Classic information in the Scrum section) - Update text on Getting Started for Intro and Latest News (SC) | 8 |
| 157 | JSW-5118 | Add option to exclude weekends from cycle time calculations | When viewing cycle time charts, weekends are included in the calculations. There should be an option to exclude weekends, if desired. (!) Testing Notes (!) Q: What if the user's timezone does not match the server timezone? A: (x) Not Answered Q: Is this setting remembered between page views? A: (x) Not Answered Q: Is it clearly specified when this option is on/off? A: (x) Not Answered Q: What happens to any events that happen in these excluded windows? Will they simply not be displayed/will they be calculated? A: (x) Not Answered Q: What if there are large outliers in the excluded period? Will the chart adjust properly? A: (x) Not Answered | 2 |
| 158 | GHS-5153 | Make CFD in RB Sprint sensitive | Add the option to refine the CFD using a sprint | 13 |
| 159 | JSW-5153 | Make CFD in RB Sprint sensitive | Add the option to refine the CFD using a sprint | 13 |
| 160 | JSW-5193 | Put add comment button the comment tab | NULL | 2 |
| 161 | JSW-5194 | Put add attachment button on attachment tab | NULL | 2 |
| 162 | JSW-5195 | Show sub tasks tab on Work mode in Rapid Board | NULL | 2 |
| 163 | JSW-5214 | Sprint Report should visually call out added and removed stories | - Styling for the Added items - Third table for Removed items - Styling for Added items do need to be possible in Removed table | 3 |
| 164 | JSW-5215 | Sort status objects in column configuration to show non zero alphabetical, divider then zero alphabetical | NULL | 2 |
| 165 | JSW-5216 | When story moved to done column don't scroll to it | Stay selected | 2 |
| 166 | JSW-5218 | When a Rapid Board is shown, add the projects shown in issues to the most recently used list in JIRA | COS: * Pool/Backlog data will now return as part of the payload a list of projects contained in the issues. This data will be expanded upon in the future. * This story will incorporate GHS-5217 * In the case where no issues are found in a backlog/pool, we determine recent projects by the query of the board ** If the query is not project-based, then we do not modify the project history * Be smart about where projects get inserted into the history * When viewing a Rapid Board via a gadget, this should not have an effect on the recent projects for the user To be smart about history, consider the following example. Viewing a board with issues from projects A, B, X and Y. The issues are seen by the board (ordered by Rank), in the order X, A, B, Y. The user's current history contains the projects in the following order (most recent first): D, B, A, F, G. Because we do not want to upset the order of projects that were already in the history and that we have just seen, the desired new ordering of projects is as follows: B, A, X, Y, D, F, G. | 8 |
| 167 | GHS-5219 | As a user, I'd like the Rapid Board to remember which board I'm on regardless of which computer I'm on | COS: - Keep the last 5 boards used on the server side - Logged in only | 5 |
| 168 | JSW-5219 | As a user, I'd like the Rapid Board to remember which board I'm on regardless of which computer I'm on | COS: - Keep the last 5 boards used on the server side - Logged in only | 5 |
| 169 | GHS-9587 | Add the ability to specify multiple board administrators so other users can change the configuration (delegated admin) | Currently only the owner or a jira-admin can do this. I think it would be good to allow this so you can have other team members adjust the settings. Currently at my company there are multiple producers on a team that all use the same board and they would like to continue to have one board for the whole team. | 5 |
| 170 | JSW-9587 | Add the ability to specify multiple board administrators so other users can change the configuration (delegated admin) | Currently only the owner or a jira-admin can do this. I think it would be good to allow this so you can have other team members adjust the settings. Currently at my company there are multiple producers on a team that all use the same board and they would like to continue to have one board for the whole team. | 5 |
| 171 | JSW-5255 | As a user I want to see all issue on the statistic burndown table, even if some don't have a statistic value | NULL | 3 |
| 172 | JSW-5268 | Perform work modes initial XHR calls in parallel | At the moment we perform three XHR calls in order to render a rapid board in series: First we get the rapid board selector data. Then we get the rapid board config data. Finally we get the issues data (allData). For the 99% case we should be able to perform all three of these calls in parallel (kick them all off at the same time), and just perform the rendering in series. This will kill off the Rapid Board selection drop down This means we will have to perform an additional two rest calls in the unlikely case where someone attempts to load a rapid board that has been deleted and gets punted to the default board. | 5 |
| 173 | JSW-5289 | As a user, I'd like the manage Rapid Board screen to have a clear 'Create new board' button directly on the screen rather than being hidden in a submenu | NULL | 1 |
| 174 | JSW-5329 | As a user, I would like a board that is not ordered by rank and therefore not draggable on PLAN mode to not show the "hand" icon or drag handles so I don't get confused | NULL | 1 |
| 175 | JSW-5330 | As a user of the PLAN mode, I would like a board that is not draggable to give me a warning when I attempt a drag like action on it and explain what the problem is | COS: - Show a warning box "Ranking is not possible because the filter for this board does not order by a rank" - Include a link to the filter section of the configuration - Discuss testing | 3 |
| 176 | JSW-5341 | Plan|Work|Report links should support opening in another tab with middle click (cmd click) | If I middle click them or Ctrl click them, they should do nothing and fallthrough to the native browser handling. We have code for this in Stash, but since we only use it with live events, we don't handle checking for left click (we probably should): EDIT: Here's with which checking as well. {code} exports.openInSameTab = function (e) { return (e.which == null || e.which === 1) && !(e.metaKey || e.ctrlKey || e.shiftKey || (e.altKey && !$.browser.msie)); }; {code} Called like {code} $(document).on('click', 'a', function(e) { if (!openInSameTab(e)) return; ... do stuff ... e.preventDefault(); }); {code} If you want to handle left click only, I believe you can check e.which === 1, but you should test that first. | 3 |
| 177 | JSW-5348 | As a user of the WORK mode, I would like a board that is not rankable to give me a warning when I attempt a rank like action on it and explain what the problem is | COS: - Discuss testing | 5 |
| 178 | JSW-5413 | Expand / Collapse All Swimlanes on the Rapid Board | Rather than just having the individual swimlane expand / collapse function, it will be convenient to have the expand / collapse all the swimlanes in one go. COS: - Menu items will appear at the bottom of the Tools menu - Include a keyboard shortcut for toggling expand/collapse all - Decide on a keyboard shortcut (Current choice is {{MINUS SIGN}}) | 2 |
| 179 | JSW-5418 | As support, I need an itemized list of the remaining time/items at the end of the Sprint in the burndown | - With 45 issues doing this manually is very painful (particularly when you're trying to reconcile history) | 2 |
| 180 | JSW-5542 | As a multi-team one backlog user, I'd like to be able to start multiple sprints at once | (!) Testing Notes (!) Q: How many sprints can be open at once? A: No limit Q: Is there any impact on reporting when multiple sprints are active? A: (x) Not answered Q: How do we know which report to jump to when juggling sprints in work mode? A: (x) Not answered Q: What happens when an active sprint is closed by some other user while you are working on it? A: (x) Not answered Q: What if i want to view different swimlane strategies in each of my active sprints? A: Raise a feature request Q: What happens when all issues are removed from an active sprint? A: Existing problem, iirc there's an open bug to better handle this Q: What if all issues from one sprint are moved to another active sprint? A: As above Q: Do we still jump to reports if an active sprint is still open? A: (x) Not answered | 3 |
| 181 | JSW-5543 | As a multi-team one backlog user, I'd like to be able to pick which sprint I'm looking at on work mode (possibly quickfilters?) | https://extranet.atlassian.com/display/GHDEV/GHS-5543+Sprint+Picker | 5 |
| 182 | JSW-5544 | As a multi-team one backlog user, I'd like to be able to pick which sprint to finish when I close one | COS: - Display inline dialog with name, start and end date - Button to finish | 5 |
| 183 | JSW-5545 | As a forward planner, I'd like to be able to name future sprints | NULL | 5 |
| 184 | GHS-5546 | Store sprint created date and show on the burndown chart data table as the first line | COS: - For historical sprints do not show this entry in the burndown | 3 |
| 185 | JSW-5546 | Store sprint created date and show on the burndown chart data table as the first line | COS: - For historical sprints do not show this entry in the burndown | 3 |
| 186 | JSW-5567 | Allow more than one plugin to register to have a tab in the detail view, use icons in the tab header | NULL | 1 |
| 187 | JSW-5568 | As a user, I'd like the board to poll for staleness and provide a notification if there are changes at a sane interval | COS: - Detect when page loses focus and stop doing this so regularly (!) Testing Notes (!) Q: How often does this poll? Can the user define this polling interval? A: 30 sec. No, user can't define interval Q: What if there was a change, then another change to undo that change? aka there is no effective delta? A: The client side will receive the updated data and then decide its already up to date, thus ignore it Q: What if the user has been logged out? A: Thanks to Jason a separate logic automatically redirects to the login page when an ajax request fails due to being logged out. This works for all requests, be it filter change, detail view, or update poller. The question here probably is whether the update poller should really trigger this redirect... Q: What if the user does not have permission to see the board? Do they still get notifications? A: Why would the board open if they had no permission Q: Any conflict if there was an error on the page as well? A: Not handled Q: Is there a way for a user to disable these notifications? A: No Q: Any conflict if I have multiple boards open in multiple tabs? A: Should not. Each board will separately poll for updates though | 8 |
| 188 | GHS-5569 | As a user, I would like to be able use the work mode while an update is being performed (kill the spinner) | COS: - Allow re-rank - Allow quick filter | 8 |
| 189 | JSW-5569 | As a user, I would like to be able use the work mode while an update is being performed (kill the spinner) | COS: - Allow re-rank - Allow quick filter | 8 |
| 190 | JSW-5583 | As a user, I'd like to have a recent version of JIM automatically installed for me | NULL | 8 |
| 191 | JSW-5603 | As a supporter, I'd like exceptions to be collapsed by default, to allow users to continue to use the app without having a large error box on the screen | COS: - A link to "Read More" will expand the container to the full height. - The box can be collapsed again. | 3 |
| 192 | JSW-5616 | As a user I want to be able to see the Remaining Estimate on Rapid Board cards instead of the Original Time Estimate | You would normally only look at a sprint board once the sprint has started, and when a sprint has started the only valu ethat is relevant for any given sprint task is the remaining estimate. Therefore this should be visible directly on the rapid board cards in stead of the Original Time Estimate. This will give a far better overview of the sprint, when viewing the entire Rapid Board. As a bonus it would be very nice if the value is editable directly on the Rapid Board cards. COS: - On work mode the lozenge will show remaining estimate - For parent stores this will not include sub tasks - Only if time tracking is enabled | 2 |
| 193 | JSW-5619 | As a user, I'd like to see the count of visible (i.e. unfiltered) issues in the column header | (!) Testing Notes (!) Q: Any limit on the number of digits? A: (/) Issue count should be unlimited (constraints currently limited to 999). Q: Takes into account when multiple filters are on? A: (/) Yes Q: Properly hides issues that are hidden for a particular user? A: (/) for browse permissions Q: Looks good in all browsers? A: (/) Yes Q: Looks good in wallboard mode? A: (/) yes | 2 |
| 194 | JSW-5660 | As a user I want to see median time on scrum/kanban charts | This would allow people to find the median time that issues take to be fixed or to be QAed or to pass through arbitrary stages of the issue lifecycle. The median is arguably a more useful time than the mean as it is less influenced by outliers. | 1 |
| 195 | GHS-5686 | As a user, during the create board process I want to select a board type first then either a filter or projects as a second step | NULL | 5 |
| 196 | JSW-5686 | As a user, during the create board process I want to select a board type first then either a filter or projects as a second step | NULL | 5 |
| 197 | GHS-5690 | As a user, I'd like to be able to inline edit the components, fix version and affects version fields in the detail view | COS: - Use the Frother control for entering input (i.e. same experience as View Issue)? | 5 |
| 198 | JSW-5690 | As a user, I'd like to be able to inline edit the components, fix version and affects version fields in the detail view | COS: - Use the Frother control for entering input (i.e. same experience as View Issue)? | 5 |
| 199 | JSW-5691 | As a user, I'd like to know in the filter configuration tab that some issues that match my filter are not appearing on my screen because they are not in a column | COS: - Something in the filter tab - Click through to the column tab (!) Testing Notes (!) Q: Alert? Dialog? Dismissable? A: Warning, shown in Filter tab. Not dismissable. Q: Count of issues not displayed? A: Nope Q: Do you get this message as soon as there exists an issue which is unmapped? A: Whenever you view the filters tab and there is an issue unmapped (current user). Other users on page refresh/load of configuration. Q: Is this only for statuses that currently have issues in them, or any unmapped status? A: Only unmapped statuses that have issues in them. Q: Does the message immediately disappear when the last applicable status becomes mapped? A: Yes, once you fix the last unmapped status with issues, then view the filters tab, it no longer appears (current user). Other users on page refresh/load of configuration. | 3 |
| 200 | JSW-5703 | When automatically choosing a name for the next sprint, increment the number at the end even when there are word characters or punctuation | Some examples * Sprint 1 -> Sprint 2 * Stash M1 -> Stash M2 * JIRA 5.0.1 -> JIRA 5.0.2 | 1 |
| 201 | JSW-5735 | As a rapid board user, I'd like to be able add/remove text custom fields to the bottom of the detail section of the detail view | COS: - Configuration per board -- New tab in config page - Any text custom field in the system -- Double check that fields for Estimation are not filtered based on issues in board - Text custom field will be read only on detail view - Add and remove fields -- If possible - reordering of fields - Fields are displayed at the *bottom* of the *top* section on the *Details* tab i.e. underneath Fix Version - Read only display for now (!) Testing Notes (!) _(Answers by mtokar)_ Q: How many text fields will we allow? A: Unlimited - as many as there are in the system to be added Q: Which text fields will be allowed, and are there any that are prohibited? A: Only Custom Fields which are of a "text" type - in the standard custom field types this means Text Area, Small Text and URL Q: What happens if the name of the attached field is modified? A: Nothing should happen - field is assigned by ID Q: Who has permission to add these fields? A: Board owner and admins Q: Are these fields added per board, or per project, or global? A: Per board Q: What happens when we remove then re-add a text field? A: It will be in a different position to before, but otherwise nothing. Q: What if a user does not have permission to see the attached field? A: There are no user permissions for fields. But if the field is not applicable in the scope of the selected issue (i.e. it is not configured for that issue type or project), then it will not be displayed on the detail view. Regardless of scope, all text custom fields are available to be added (if they have not already been added). Q: If a field is added while a user has the detail view open, do we require a full page reload or just a detail view refresh to see it? A: Just reload detail view. Q: Can users add GreenHopper fields to the details tab? This could lead to odd behavior in the case of Story Points. A: No special GreenHopper fields are currently allowed to be added. Q: Will we only allow text fields, or number fields as well? A: At the moment only text fields Q: Will these fields be inline editable in the detail view? A: At the moment read-only. Q: Will these fields be XSS safe? A: They should be, yes. | 13 |
| 202 | JSW-5737 | As a user, I want to link scipe to stories | COS: - New link type - Need service to link/unlink - Only valid between an Epic issue type and a Story issue type | 5 |
| 203 | JSW-5771 | XML view for issue contains empty value for field SPRINT | If the SPRINT field contains value and is correctly displayed on the issue screen, click Views->XML. The xml contains information about the SPRINT customfield but its value is empty. This bug causes following issue with IDE Connectors: * user opens issue in the IDE Connector (it is based on the issue XML view and contains information that Sprint value is empty) * user makes changes and submit issue with the Sprint value empty * the Sprint value is erased on the JIRA side (ups!) | 1 |
| 204 | JSW-5773 | Ability to use the Upcoming Sprint value or name in JQL searches | I'd like to have the ability to use the notion of Upcoming sprint in JQL searches. For instance, I have planned 2 sprints ahead of the current open sprint. I'd like to be able to filter separately the issues planned in upcoming sprints 1 & 2, using the advanced search. I would use this search query to create swimlanes in Kanban boards or create structures within the Structure plugin. Note that future sprints don't have a date so autocomplete needs to be revisited. h3. Workaround via database: https://confluence.atlassian.com/display/JIRAKB/How+to+find+issues+from+non-started+sprints | 1 |
| 205 | JSW-5831 | As a user, I would like to be able to configure the due date or any other date field on to the detail view | COS: - Due Date - Resolution Date - Custom fields of date type - Second restful table for dates - Go in to the dates section (!) Testing Notes (!) Q: Be sure to test with Greek and Korean dates A: (x) Not Answered Q: What if the selected day is a non-working day? A: (x) Not Answered Q: What happens when you change the JIRA date format with the field in place? A: (x) Not Answered Q: How many dates fields can you add to the detail view? A: (x) Not Answered | 5 |
| 206 | JSW-5832 | As a user, I would like to be able to configure the business value (or any other numeric field) to be shown on the detail view | COS: - Business Value - Custom fields of type numeric - If the same as the estimate statistic do not offer it to add -- If already added, show a warning in the configuration page, and do not show in Detail View on board Testing: - Kanban vs Scrum boards - story points are handled differently (!) Testing Notes (!) Q: What if you add business value when it is already the selected estimate field? A: The currently selected estimate field should not appear in the dropdown list. The only time it does if if you change the estimate field then click Issue Detail tab without refreshing the page. In this case, it does nothing when you try to add it. Q: What if you added business value before setting it as the estimate statistic? A: It does not appear in the issue detail. When you view the configuration, there's a message against the field. Q: If we allow both, do they update properly when either of them is updated? A: (x) Not Answered (don't understand this one) Q: How many fields can we add? Are there any limitations? A: No Q: Any issues when the user cannot edit the field? A: No Q: Can you add duplicate fields? A: No Q: What happens when a number field is changed to another field type? A: I don't think this is even possible. Q: What happens if the field is deleted after it was added? A: It should show up as not valid with a message on the config page and does not show up in issue detail. Q: Any limit to the length of input to the ...? | 3 |
| 207 | JSW-5833 | As a user, I would like to be able to configure the resolution, environment and security level fields to be shown on the detail view | COS: - Resolution - Environment - Security level (!) Testing Notes (!) Only plays for this type of story include: * deleting the field when assigned -> this field is a system field so we can't delete it. I tried to hide it but we don't honour those settings (see https://jira.atlassian.com/browse/GHS-5831?focusedCommentId=412545&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-412545) * restricting permission to particular users -> the user will see an error message saying that it is not possible to access the issue after security level configuration change and on board reload the issue will not be visible in the list * checking behavior when naming fields as system-wide objects (Unassigned) and duplicates -> we can create a custom field with the same name as a system field (like resolution, environment and security level). It will be selectable in the field list in the Issue Detail View tab of the configuration page. | 2 |
| 208 | JSW-5834 | As a user, I would like to configure label, select, check, radio and version fields to be shown on the detail view | COS: - Label custom fields - Select & Multi select custom fields - Check & multi check - Radio - Version custom field (!) Testing Notes (!) Q: How many of these fields can you add? A: (/) As many as you like Q: Will these be selectable in the detail view? Or only the current state of the field? A: (/) Read-only Q: How will we display a field with multiple selections? A: (/) Comma-separated Q: Will there be any problem adding fields that have duplicate names? A: (/) No, field configuration is stored by id. It would be hard to know which one is which though | 3 |
| 209 | JSW-5835 | As a user, I would like to configure user or group custom fields to be shown on the detail view | COS: - User custom field type - Group custom field type - Another RESTful table for people section (!) Development Notes (!) Q: How many users and groups can we add to the detail view? Any limit? A: (/) No actual users or groups are added, only defined custom field containing users / groups. There is no limit on the amount of custom fields displayed Q: Where is the people section located? A: (/) In the rapid board config page, under the issue detail view tab. In the third table. Q: Are users/groups notified when they are added to a board? A: (/) They aren't actually added to the board. The issue detail view will display custom fields of a type related to people (user picker, group picker, ...). Q: What if a person/group added to the board does not have permission to see it (aka no permission to see the filter)? A: (/) The person or group does not know that he is being displayed in the issue's detail view on the rapid board. Q: Will this be a new tab on the vertical jump nav? A: (/) No, the people custom field will be displayed in the details tab of an issue detail view, under the people section (under assignee and reporter) Q: What if a user or group is deleted while displayed on the board? A: (/) The link to the person / group is displayed. If the person or group is deleted then following the link will show an appropriate error page. Q: What if a user/group is renamed? A: (/) The link will still work. The changes will be reflected on the next refresh of the data Q: Do any of these questions surprise you? If so, what hadn't you previously considered? A: (x) Not Answered | 5 |
| 210 | JSW-5841 | As on ondemand user I want to be able to use sample data | NULL | 1 |
| 211 | JSW-5843 | As a use GH should create OD compliant projects. From the welcome mat it does not respect all-app-access requirement in ondemand | Code to be copied from https://bitbucket.org/wseliga/jira-ondemand-jim-bridge-plugin See https://studio.atlassian.com/browse/JIM-691 for more details | 3 |
| 212 | JSW-5875 | As a user, I'd like basic flagging of issues | This is just the first step in flagging COS: - Flag is set / cleared from the cog menu in detail view & context menu - Flag icon takes place of issue priority - background color change when issue flagged (also specific color when selected) - Appear in work mode and plan mode - use the flag field introduced in classic mode : -- not empty -> flagged -- empty -> un flagged - in case of mixed selection propose "flag" action, else propose the opposite action of the selection - in case of multiple issues flagging with error : -- flag the one that can be modified -- display a list of info message "issue key -> error" | 3 |
| 213 | JSW-5877 | As a user, I'd like the existing fields included by default in the detail view to be configurable like for custom fields | COS: - Upgrade task - All the existing fields on the detail tab of the detail view in the same order they are there atm - Newly created boards should have the default set up NOTE: We should lock the Rapid View when an upgrade is in progress. (!) Development Notes (!) Q: What if one of these fields does not exist? A: (/) Not possible to delete, but you can hide the field. It is not visible on detail view, but its listed on the detail view configuration. Q: What if one of these fields has been renamed? A: (/) No rename option available for system fields Q: What if there is a custom field named with same name? A: (/) No special handling in this case - works as expected. Q: Is there any difference for in-line editable fields vs non-editable? A: (/) We are only doing this for fields in Detail Section Q: What happens if you remove a default field after the upgrade task? A: (/) Its not possible to delete system fields from JIRA Q: This needs to be tested on all databases. A: (/) OK Q: What older versions of the data do we need to be wary of? What about pre- Detail View data? A: (/) Should be handled automatically by AO staff Q: What if fields are not in the expected order? A: (/) The order in this case does not matter - we will add those fields which are not already present there. | 8 |
| 214 | JSW-5927 | Allow JQL for searching for all issues in an Epic via their "epic label" | * Either JQL function, or change the fundamental clause handling to allow for these labels * Use the epic label field to look up an epic and then use its ID in the Lucene query * Don't consider autocomplete (!) Testing Notes (!) Q: What if there are epics with duplicate names (either globally or within the search scope)? A: (/) They will all match so the issues list will be an union of all the issues of those matching epics Q: What if the epic is closed/resolved? A: (/) We are agnostic Q: What if the epic label is empty? (is this even possible?) A: (/) The epics with empty label won't match | 3 |
| 215 | JSW-5941 | Simplified Workflow button fails with "Workflow Migration did not complete successfully" can be improved | (!) Testing Notes (!) Q: Who has permission to simplify the workflow? Board owner or admin? A: (/) Admin or Sys Admin Q: If board owner is allowed, what if they don't have permissions to edit the workflow of the project? A: N/A Q: What if a simplified workflow already exists for this project? A: Dialog prompt is not given. Q: What about the resolve screen or modal dialogs from the last workflow? A: All screens from previous workflow are removed. Q: What will happen if the user is logged out/migration is interrupted during migration? A: We now make one call to the server via REST, to both create the new (simplified) workflow scheme and to kick off the migration of the workflow. Q: What if an issue is being transitioned during migration? A: Whatever happens in JIRA will happen here. Q: What if the user's security token is expired? A: The XSRF token will no longer be used in this operation. Q: What if the board filter is changed to include multiple projects when at the workflow migration dialog? A: I'm assuming it will fail with an error. # Deploying a fresh *JIRA 5.0.7* instance equipped with *GreenHopper 6.0.2*, tried to enable the *Simplify Workflow* button but it failed with the following error: !migrate_failed.JPG! # After that, authenticate as a user with the Administrator Access: !admin_access.JPG! # After that, the workflow migration works fine: !migrate_success.JPG! It would be useful if there is some sort of indication that shows the user does not have the Administrator Access. Perhaps next to the *Simplify Workflow* button. Workaround to this issue: [Simplified Workflow button fails with "Workflow Migration did not complete successfully"|https://confluence.atlassian.com/pages/viewpage.action?pageId=301663531] | 5 |
| 216 | JSW-5945 | Allow the detail view to be closed on plan mode | COS: - What does this look like without the "Epics" column? - The whole plan mode just goes across the screen Scenarios / Requirements * Behaviour in plan and work mode should now be more consistent ... * Plan and Work mode details are independent, i.e. when opening issue A in Plan and issue B in Work, flicking between the two should preserve the open issues. * Opening and closing details in plan and work mode are independent, i.e. closing detail in plan mode should not close it in work mode and vice versa. * On initial load, the backlog will fill the screen - the plan mode content block is gone for good. * Deselecting an issue in plan mode has the same effect as closing it. * Clicking on an issue in plan mode now just selects it and no longer opens the issue detail. However if it's already opened then it will refresh to the currently selected issue (same behaviour as work mode). * If a filter is applied and the selected issue is filtered out then issue detail is closed. * Multi-select - if issue detail is open, display the last selected issue. If it's closed, don't open it. (!) Testing Notes (!) Q: What if an inline edit is open? A: Changes should be saved and then detail closed. Q: Will it have an XBox™ to close akin to work mode? A: Oui Q: What if there is an error in plan mode when you try to close it? A: It should not close until the error is fixed. Example: Edit the estimate and put some letters in the field (not allowed) - currently the error appears inline, then on close appears at the top. Q: Do the cards resize nicely without detail view? A: They will stretch across the page Q: Same keyboard shortcut? If so, is there any collision with S + T? A: Shortcut will be T. ST should rank the issue without showing the issue detail if it's not open. If it is, ST selects the next issue that was below the one that moved so this would then appear in the detail view. Q: How performant is it with thousands of issues? A: (x) Not Answered No idea yet. | 3 |
| 217 | JSW-5994 | As a user, I'd like to inline edit sprint name, start and end date at the top of plan mode so that KA styles make sense | COS: - Dates will split to two edits - Dates will behave like existing inline edit in work mode dialog - When you edit the name you'll just be editing the name inline (!) Testing Notes (!) Q: What happens when clicking between open inline edits? A: Clicking from a name to a date picker will submit the name (if changed) and activate the edit for the date picker. Clicking between date pickers will change the currently edited date picker, as choosing a new date will automatically stop editing after the new date is saved. If there is an error in a field, clicking away from the field will not keep the field in edit mode. Q: Are foreign date formats properly supported? A: Tested with Swedish locale - there is still the AM/PM time code, but that is a JIRA issue. Q: Inline edit works in all browsers? A: (x) Not Answered | 2 |
| 218 | JSW-6011 | Make error box dismissable | NULL | 1 |
| 219 | GHS-6020 | As a scrum planner I would like the ability to reorder sprints | It would be extremely useful to be able to reorder sprints on the Plan board. Changing the sprint order would swap the relative order of all of the issues contained in those sprints. In addition to improving Scrum planning, this would resolve a critical missing feature available in the Classic boards where the Version cards could be re-ordered by giving equivalent functionality in the Rapid Board. | 5 |
| 220 | JSW-6020 | As a scrum planner I would like the ability to reorder sprints | It would be extremely useful to be able to reorder sprints on the Plan board. Changing the sprint order would swap the relative order of all of the issues contained in those sprints. In addition to improving Scrum planning, this would resolve a critical missing feature available in the Classic boards where the Version cards could be re-ordered by giving equivalent functionality in the Rapid Board. | 5 |
| 221 | JSW-6037 | Restrict editing of the Sprint CF to users with Schedule permission for that issue | This is something I found randomly and I guess it makes sense for us to check. I tried this on a clean installation and reproduced many times in different ways. In a nutshell, I think the shortest path to demonstrate is the following: # Let us say I have a project named _ABC_ and a Rapid Board _ABC Board_ containing issues from that project. # I also have two users: ## charlie: All permissions on project ABC ## alpha: Only in jira-users, essentially only able to create issues in ABC (user has been added specifically in this example but it would work for him anyway): !1-alphagroups.png! !2-createissues.png! # Project roles in ABC are like the following: !3-people.png! # charlie creates ABC-1: !4-create.png! # Then charlie adds ABC-1 to Sprint 1 (just created by him, also): !5-plan.png! # The sprint id for that sprint is 1 (the address bar is from the sprint report): !6-sprintId.png! # The Sprint field is also visible on all screens: !7-sprintfield.png! # Now user _alpha_ tries to create an issue in JIRA. Remember that he cannot even browse project ABC but he can edit the Sprint Field and add the sprint id (1, in this case): !8-alphacreatesissue.png! # ... so when he tries to view ABC-2 he cannot: !9-permissionviolation.png! # However, ABC-2 has been added to the sprint: !10-issueadded.png! Should this be possible? Am I missing something, perhaps? | 3 |
| 222 | JSW-6073 | Add Epic Label to the Create Issue Screen in JIRA config so it will show up in the Epic Quick Create dialog | (!) Testing Notes (!) Q: What happens if this field is deleted/removed from the screen? A: It won't appear on the screen. Q: What if it is renamed? A: In theory, it should just display with the new name but atm, GH blows up and disables itself. See subtask GHS-6162. Q: What if the field's permissions are modified? A: It doesn't show up. Further testing notes: - the field is added to the screen for the create issue operation for the epic issue type - it's not added to screens within an issue type screen scheme that is not associated to any projects - if there is a specific screen scheme for epics, it's only added to those screens - otherwise screens within the default scheme | 1 |
| 223 | JSW-6077 | Create labs feature to enable Epic support | COS: - Add flag - Wrap existing prototype code with a check for the flag - Convert the creation of Epic related fields to be on the switch of this flag as opposed to the current update task approach (!) Testing Notes (!) Q: What happens to Epics fields if Labs is disabled after enabling? A: The fields remain in the system, as we don't delete fields Q: What if those fields are deleted after Labs is disabled? A: The field won't be recreated as it isn't used anymore Q: And what if a user again re-enables Labs? A: All missing fields are created/recreated upon first usage Q:If Epic Labs is disabled, can I still interact with previously created Epics? A: Yes, but they show up as normal issues inside the backlog | 3 |
| 224 | JSW-6078 | Plan mode layout for 3 panels (to bring in the closable detail view and allow closable Epic panel) | (!) Testing Notes (!) Q: Need to test all states: Matrix of Epics open/populated, issues in backlog exist/don't exist, and Detail view open/closed/help text A: (x) Not Answered Q: Check above at minimum resolution A: (x) Not Answered Q: Look for overlapping panels, and try with long but reasonable length data in relevantly displayed fields. A: (x) Not Answered | 2 |
| 225 | JSW-6079 | Temporary tools menu option to hide/show Epics (only on plan mode) | (!) Testing Notes (!) Q: What does temporary mean and how will a user know that? If they get used to it, and it disappears, they will be >:/ A: (/) that's why it's Labs™ Q: Does this interact with the Epics sidebar twixie? A: (x) The toggle menu state reflects the current state of the Epic Panel (see GHS-6179) Q: If so, do they play nicely together? A: (x) Yes Q: Does hide/show mean the entire panel and twixie go away, or does it actually mean expand/collapse? A: (x) Expand/Collapse Q: Must test with all states of pan mode: Epics expanded/collapsed/populated/un-populated, backlog empty/filled, detail view open/closed A: (x) Not Answered Q: What happens when jumping to Work and Report mode and back? A: (x) Persists Q: Is this persisted across logins/users? A: (x) I think each user should own his/her own state Q: Who has permission to do this? Can non-admin or anonymous users do this? A: (x) Anyone | 2 |
| 226 | JSW-6080 | Make sure that Epics do not get included in to the sprint (at the moment they are in the backlog and get put in to a sprint) | COS: - Epic should not be in the backlog list - When starting a sprint Epics are NOT included (!) Testing Notes (!) Q: Check that Epics are not draggable into the backlog area. A: if the epics feature is enabled, no epic is available in the backlog list and then you can not drag and drop it. If the feature is disabled then you can drag and drop the epics like any issue type (bug, story etc.) | 1 |
| 227 | JSW-6081 | Drop down on Epic with View in JIRA link | COS: - Implement drop down menu - Include View in JIRA link in there - Middle/Cmd click open in new tab works (!) Testing Notes (!) Q: Make sure open drop down handles (x) Epics panel closing (x) dragging issues within backlog and to epics (x) quick/instant filter (x) switching modes (x) open/closing of detail view (x) inline edits (x) any of the other dropdowns opening | 2 |
| 228 | JSW-6082 | Allow a story to be unassigned from any Epic | Minimum Criteria: - Cross on booger - No warning on removal -Goal is to work with design to actually design this before implementation- (!) Testing Notes (!) Q: Who can remove from an epic? A: (/) Only the admin Q: What if the epic itself is deleted? Are stories automatically unassigned from it? A: (/) Yes Q: What if the issue is not currently visible due to filter/column mapping? A: (/) If an issue is not visible, you have no mechanism to unassigne it | 1 |
| 229 | JSW-6083 | Implement estimated vs unestimated stories progress bar | COS: - Coloured section of bar is the number of issues that have an estimate applied, uncoloured (line) section of the bar is the count of issues with no estimate applied - Tooltip shows both issue counts and %'s - Put in expanded Epic information panel unestimated and estimated (!) Testing Notes (!) Q: How will this handle filtered issues? A: Ignores filtering Q: What if there are no stories in the epic, or only 1? A: The bar will not show for zero, will be small if % is small Q: What if no estimate statistic is selected for the board? A: One is always selected Q: What if stories are removed from the sprint? A: (x) Not Answered Q: What happens when the last one gets removed? A: (x) Not Answered Q: And another one added after that? A: (x) Not Answered | 2 |
| 230 | JSW-6084 | Implement the estimate done vs estimate undone progress bar | COS: - Green is the sum of the estimate value for the completed stories, the line (unfilled section) is the sum of the estimate value for the incompleted stories - Tooltip shows both estimate sums and %'s - Put in expanded Epic information panel (!) Testing Notes (!) Q: How will this handle filtered issues? A: (x) Doesn't change Q: What happens to the bar if there is no estimation statistic for the board? A: (x) There always is Q: What if a non-story points estimate is chosen? A: (x) The bar should represent the completed % of whatever estimate statistic is used. Q: What if there are no stories to estimate, or there's only 1? A: (x) If there are no stories it shows as completed (nothing left outstanding right?) If there are no stories estimated it shows as completed unless the estimation statistic is issue count. If there's one story with an estimate incompleted it shows as empty. Q: What about the estimates on subtasks? Are those summed as well? A: (x) No. These are used only for remaining estimate. Q: Does the bar update if an invalid estimate is entered? A: (x) No Q: Does the bar update on estimate change of a story in the sprint? A: (x) You can't change an estimate of a story in a sprint once it's started. If it hasn't started then yes. Q: Does the bar update on drag of a story into the sprint? A: (x) No, only on stories being completed or added into an epic. | 3 |
| 231 | JSW-6085 | Make expanded status of Epic sticky | COS: - Not included in URL - Does store expanded state of multiple Epics | 2 |
| 232 | JSW-6086 | Make selected status of Epic remembered | COS: - Include in the URL - In addition to the selected status of an issue Discussion: Selection states across tiered items: parent/child - Mimic some common approaches like mail clients - folder can be selected, when child item is selected, folder has a "secondary selection" that shows it is still active, but not the active selection. Bringing up details - Thinking about this further in light of showing the Epic "details" on the right, I don't think we want to do this on Select of the Epic. That should be a primary action that is to filter the backlog list. It may be worthwhile to add a "details" affordance though to manually display the issue details for an epic (just not on epic selection). I'll add that to the next iteration of the design. | 3 |
| 233 | JSW-6087 | Multiple select for Epic filtering | This may be an additional story, but I had shown some designs around giving users an additional way of knowing the backlog was filtered by Epic - originally I had put the epic label on the headers of backlog containers (sprints and backlog) but that might be problematic. Martin had suggested re-using the active quickfilters area, which has merit. Will add design task to explore. | 2 |
| 234 | JSW-6090 | Allow editing of the colour swatch for an Epic | COS: - Fixed palette to start with - Requires edit issue permission - Use the colour custom field we have created (!) Testing Notes (!) Q: How does an open colour picker interact with the following: Clicking other inline edits (x) Closing the epics or detail panel (x) Switching modes (x) Drag and Drop (x) Create/Delete sprints (x) Reordering epics (x) Multi-select (x) Opening the tools menu (x) Applying quick/instant filters(x) Creating a new issue (x) Create a new epic (x) Anything I'm missing (?) Q: What if the exact same colour is chosen as another epic? A: (x) Not Answered Q: Are default colours still rotated? A: (x) Not Answered Q: | 5 |
| 235 | JSW-6091 | Show Epic label in detail view for story | COS: - Show in both plan and work mode - Don't show it on sub tasks (!) Testing Notes (!) Q: Make sure detail view updated after label update/removal A: (x) Not Answered Q: Will tasks or improvements get labels too? A: (x) Not Answered Q: Make sure color is updated correctly too A: (x) Don't need to worry about colour for now, this is a text only representation. | 1 |
| 236 | JSW-6110 | Add 'Enable Epic Labs' box on to Getting Started screen (like it was for Scrum support) | (!) Testing Notes (!) (x) Be sure to check the visibility for this with admin, non-admin, and anonymous permissions - Non-admin and anon should be the same (x) Be sure to check multiple on-off | 2 |
| 237 | JSW-6128 | Have checkboxes in board configuration for Burndown to specify days that are not working days, shade that area of the graph and have the guideline be level at that point | - Default on new boards is not to show sat / sunday in the timezone of the server - Affects burndown chart only (and mini burndown in sprint report) - Default to timezone of server but allow to be changed - Display timezone being used - New reports tab in configuration - Allow additional days to be specified - If JIRA has a weekend setting use that for the default (rather than just Sat/Sun) (!) Development Notes (!) Q: Must test when there is a switch-over from standard time to daylight savings. A: (x) Not Tested Q: What if the non-working days are not valid? A: (x) Not Answered Q: What if all days are marked as non-working days? A: (x) Not Tested Q: What if the sprint starts or ends on a non-working day? A: (x) Not Tested Q: Is there support for defining which days are your weekend? aka the Saudi case A: (x) Not Answered Q: Is the chart displayed in the client's timezone, the user's timezone (from profile), or server? Chart should line up with the sprint dates. A: (x) Not Answered Q: What if there are datapoints in a non-working day time period (shaded area)? Are they treated the same or excluded? A: (x) Not Tested Q: What if 2 non-working periods overlap? A: (x) Not Answered Q: Do any of these questions surprise you? If so, what hadn't you previously considered? A: (x) Not Answered | 8 |
| 238 | JSW-6152 | As a GH developer, I would like for the custom fields that GH creates to appear as "managed" in JIRA's administration interface | FINAL BEHAVIOR: 1. For fields with options (epic status): If everything is 1:1 like the original configuration, then lock the field, otherwise don't lock the field 1a. Unless there is all projects/appropriate issues field scheme with ZERO options in there. In that case we will just add the options. 1b. Unless there are no schemes, in which case we introduce our own. 2. For fields without option fix up the contexts then lock the field 3. do NOT fix up field names/descriptions for any of the fields 3a. But fix the searcher. 4. for the Rank field, change managed level to "admin" (field creation) plus a message that the field should normally not be created as GH creates the field 5. The default rank field should be fixed up in context and then locked. In JIRA 5.2 there is a new API around Managed Configuration Items. This allows a plugin to specify that instances of custom fields, and custom field types, are "managed" by the plugin and should not be modified/created by administrators. Fields to be restricted (no edit, no create): All Issue Types/Global Context: - Epic Link(show) - Sprint(show) - Rank(show) Epics only/Global Context - Epic Status(show) - Epic Name(show/require/renderer - default text) - Epic Color(show) We must also ensure that existing fields are in the correct configuration before locking them down. (!) Development Notes (!) Q: Is fixVersions one of these since we rely on it for release planning? A: (/) No - it is a system field provided by JIRA and therefore should be locked by definition. Q: Rank field? A: (/) Also fix/lock the default rank field | 3 |
| 239 | JSW-6212 | As a user, I would like to add issues in an active sprint to an epic | COS: - Allow dragging of the story but make sure that the droppable area in the backlog does not indicate anything that might make the user think they were dropping the story from the sprint (!) Testing Notes (!) Q: Can you multi-select issues and drag them into an epic from the active sprint? A: (/) Yes Q: What if you multi-select issues from both the active sprint and from the backlog and drag to an epic? A: (x) We can't do that, should we ? Q: What if the epics panel is collapsed and you drag to it? A: (/) Works the same way it would if it was open Q: What happens when you drag to the edges of the screen? A: (/) If there is non visible space it scrolls, nothing else Q: What if the issues from the active sprint are already in another epic when you drag to a new one? A: (/) The issue is affected to the new epic Q: What if a quick/instant filter is on while dragging? A: (/) Issues are filtered out and not selectable Q: Any difference if the Epic is expanded or collapsed? A: (/) No | 3 |
| 240 | JSW-6232 | Allow inline edit of Epic label | (!) Testing Notes (!) Q: Make sure to test opening the inline edit, making a change, and the following actions: Clicking other inline edits (x) Closing the epics or detail panel (x) Switching modes (x) Drag and Drop (x) Create/Delete sprints (x) Reordering epics (x) Multi-select (x) Opening the tools menu (x) Applying quick/instant filters(x) Creating a new issue (x) Create a new epic (x) Anything I'm missing (?) Q: Test that foreign character's work A: (/) UTF-8 characters work; no XSS Q: Try long but reasonable input A: (/) Input is limited to a reasonable length Q: Does tab submit as well? A: (/) Yes but does not initiate inline edit of next epic, which I think is okay | 5 |
| 241 | JSW-6237 | As a user, I would like to see some feedback after creating an epic on Plan Mode | * Show a success message with a link to the issue view Must be applied both when "Create epic" button is used as well as regular Quick Create / C keyboard shortcut. (!) Testing Notes (!) Q: What if the epic was added to another project not on the board? A: The message is displayed Q: What if the board is multi-project and an epic is added to one of these projects? A: The message is shown regardless of whether the epic is on the screen or not | 1 |
| 242 | JSW-6294 | Improve epic linking code to not perform multiple re-indexes | Once JRA-30144 is completed, code changes are required in order to opt-out if indexing on createIssueLink and removeIssueLink, collect the issues that require re-indexing and perform a bulk re-index on all those issues at the end of the operation. | 5 |
| 243 | JSW-6308 | Restore the feedback link in the ROTP header | COS: - Put at bottom like 'Give Feedback' in JIRA - Continue saying 'Give GreenHopper Feedback' - Apply same treatment to BTF | 1 |
| 244 | JSW-6312 | Implement 'Jump Nav' (vertical icons for tabs which jump to the part on the continuous page) | COS: - Implement icon bar on the left - Continuous page - Headings for sections that didn't have headings before (i.e. a heading for each tab) - Selection status for visible section - Clicking on the icon scrolls to that section - Remembered state of the Detail View when navigating through issues or modes (current functionality - don't break it!) (!) Development Notes (!) Q: Make sure this plays well with all existing functionality, such as keyboard shortcuts and moving tabs. A: (/) We need to remember the currently selected 'tab' when moving to the next issue or returning to the mode. Q: How do third party icons affect this layout? A: (/) The icons will occupy the same space which is a maximum of 16px x 16px Q: How will resizing of large inline edit fields like the Description field play with the new continuous page and jump navs? A: (/) It will move the content below relative to the change in size. Q: Will users be able to switch back if they don't like it? A: (/) They'll all like it ;-) There is no option for legacy versions, only for continuous improvement. Q: Do the jump navs work ok when zoomed and at all supported window sizes? A: (/) Window size should not make a difference, though resizing will be taken into account for the size of the detail view content. Q: Does tabbing through the tabs still work? A: (/) They won't be tabs, but they'll be accessible using the tab key as before. Q: What if some fields are hidden from the default screen (like Description)? A: (x) They should be hidden. R: Please test this. Q: Are the icons always hidden when the detail view is closed? Should they be displayed? A: (/) They will be hidden since they are within the container that is removed. Q: What happens when the item counts exceed the available space? A: (/) Unlikely with expected usage but expected behaviour is to overflow into content area. Clipping or ellipsis would not help much. We can fit 5 digit numbers before this occurs. Q: What happens when the nav items exceed the available space? A: (/) Unlikely with expected usage but possible as there's a plugin point there. After a point they would be clipped and unavailable to click. Content can be accessed by scrolling. Q: Does the Detail View render ok when no issue is selected? A: (/) Yes, note the DV has a single column in this state for Plan mode. In Work mode it closes. | 8 |
| 245 | JSW-6313 | As a user, I want improved performance of epic issue statistics updates because I want up-to-date data | Currently on GDOG, dragging 4 issues into an epic takes ~10 seconds for the issue count in the epic to update. (?) This will need to update *all* statistics shown for a given epic -- see comments. (!) Testing Notes (!) Q: We should write a soke test for this and try out the difference before and after the changes with varying sizes of data. A: (x) Not Answered Q: What calculations will be made on the client side? A: (x) Not Answered Q: Will these calculations impact other client side operations, or otherwise affect responsiveness? A: (x) Not Answered Q: Will need to be checked in all browsers. A: (x) Not Answered | 5 |
| 246 | JSW-6339 | Allow the use of Sprint name in JQL to find issues in a sprint | COS: - Must autocomplete -- Autocomplete options are rendered with *Sprint Name - Start Date (ID)* -- When choosing an option from autocomplete, it boils down to the sprint ID - Must accept 'sprint = "name"' (even if they are not unique) and 'sprint = id' | 5 |
| 247 | JSW-6346 | Epic Label requireness must apply to all relevant Field Configurations, not just the Default | Currently, the "Epic Label" field is only made "Required" in the Default Field Configuration. This logic needs to change to include any Field Configuration that is used for the Epic issue type in a project. (!) Testing Notes (!) Q: Does this logic also extend to recreation of the Epic Label field after it is deleted? A: (/) Yes. When the field is re-created it is again made Required. Q: What if there is another field/scheme with a duplicate name? Are we referencing both by ID? A: (/) Field configurations are referenced by ID. | 3 |
| 248 | JSW-6355 | XSRF in com.pyxis.greenhopper.jira.actions.VersionBoardAction | NULL | 2 |
| 249 | JSW-6356 | XSRF com.pyxis.greenhopper.jira.actions.TaskBoardAction | NULL | 2 |
| 250 | JSW-6370 | As a user, I would like for "Done" epics to not show up in Plan Mode | This would be based on the value of the Epic Status field, not the workflow status. See sub-task re: writing an upgrade task. COS: - Show a confirmation dialog when a user updates an Epic to done in Plan mode (y) This has been done as part of GHS-6372 - Upgrade task to convert all existing Epics with a resolution set to have Epic Status or Done, any existing Epics with no status set to ToDo - Epic label on an issue (and in detail view) should still show even if the parent is not shown in the Epic panel | 3 |
| 251 | JSW-6372 | As a user, I would like to easily see and update the Epic Status of an epic in Plan Mode | COS: - Single menu item to mark as done with confirmation dialog (!) Testing Notes (!) Q: Can you reopen the epic via the same menu? A: (/) No. You must reopen the epic via JIRA View Issue. Q: Test when Epic status is stale/out of date. Try updating and dragging epic around. A: (/) Marking an epic as Done when the state is stale will have no ill effect, as the issue still exists. Ranking similarly is okay. Adding an issue to an epic that has since been removed will work but then afterwards the epic will disappear. Q: What happens when the last issue in a completed epic is deleted/removed? A: (/) Behaves as normal? Q: Will updating the status affect quick/instant filters on that epic? A: (/) If an epic is selected (filtering active) and then marked as done, that filter will be removed. Should not affect any other filters. Q: Can you change the statuses of the epic in any way? Deleting, renaming the status and messing up the epic? A: (/) Yes - the "options" are configurable from JIRA's Custom Field admin UI (Configure). It will continue to work until there is only one option left. It will pick the "last" option as the one to set when marking as Done. | 3 |
| 252 | JSW-6377 | As a user, I would like to display the number of votes in the agile board. | As we use the voting facility of JIRA/Greenhopper to get a guideline when ordering/ranking the backlog in Planning mode in the agile board, we would love to see the number of votes on the agile board (only planning mode). For this prupose we could go into two directions: * display the number of votes in all cards in the backlog (configurable?) * display the number of votes in the detail view of the agile board. The latter is acceptable and probably easier to get. We recommend put this in the People section of the Info area. We'll link the tally directly to the voters page just as JIRA View Issue does. | 1 |
| 253 | JSW-6389 | As a user I would like to see which issues are not linked to an Epic in the plan mode | It would be awesome to have an entry on the Epic area, let's call it 'Ungrouped', which when clicked shows all the items which are not mapped to an Epic. Found that it is painful to scroll down the entire backlog to find the right issue, click and drag it all the way to top to drop it to the right Epic issue. - When an item is dragged and dropped on it, it will be unassociated from any Epic it's currently connected to (!) Development Notes (!) Q: What happens to this item when there are no epics assigned to it? Will there be a way to tell it is empty without selecting it? A: (/) No, it does not have a count. Q: So clicking the x on an epic link will automatically add that issue to the unlinked epic? A: (/) Correct (v good note) Q: Will the unlinked epic update with the new addition in the case above if it is currently selected? A: (/) Yes Q: Will this only include issues within the backlog or also issues in the work mode? A: (/) Epic filtering is for all issues in Plan mode so includes active sprints listed at top Q: Does the board require a refresh in order to display these newly linked issues? A: (/) Uses same update as epic filtering = not a full page reload | 1 |
| 254 | GHS-6391 | All Epic Progress Report | Show the status of each Epic in the board, along with the number of stories, complete vs incomplete, estimated vs unestimated Include done Epics Link from each Epic to the Single Epic Report for that Epic | 5 |
| 255 | JSW-6391 | All Epic Progress Report | Show the status of each Epic in the board, along with the number of stories, complete vs incomplete, estimated vs unestimated Include done Epics Link from each Epic to the Single Epic Report for that Epic | 5 |
| 256 | JSW-6392 | Single Epic Progress Report | There will be an Epic Report with three sections: - 1: Epic progress chart ** Starts at epic creation time ** finishes on current date ** line for issue count ** line for unestimated issue count ** line for total amount of estimated work (using selected estimation statistic) ** line for completed work (using selected estimation statistic) ** tooltips will be like the sprint burndown ** show non-working days markings This means we have two vertical scales (count and estimate) - 2: Summary of current epic status ** Looks like the current statistics in the plan mode - 3: Table showing all issues currently assigned with the current status (done in GHS-6616) (!) Testing Notes (!) Q: What happens with stories that were moved/deleted/converted to subtasks and vice versa, and how is this displayed in the table? A: (x) Not Answered Q: Are there any maximums to the table length, in terms of issuekey/number of issues/etc? Can you break these limits? A: (x) Not Answered Q: What if the Epic itself was closed/done then reopened? Is the report still available and is there any indication about this history? A: (x) Not Answered Q: What if editing another issuetype into an epic or vice versa? A: (x) Not Answered Q: Are reports generated dynamically? A: (x) Not Answered Q: What happens if I visit the report URL for another non-epic? A: (x) Not Answered | 8 |
| 257 | GHS-6404 | As a user, I would like a quick link to an epic's Epic Report on the View Issue page | Once the Epic Report has been implemented, have a link in the Agile web panel to open the report for the current epic. Like sprint links, it should open a dialog with the board options if there are multiple boards. | 2 |
| 258 | JSW-6404 | As a user, I would like a quick link to an epic's Epic Report on the View Issue page | Once the Epic Report has been implemented, have a link in the Agile web panel to open the report for the current epic. Like sprint links, it should open a dialog with the board options if there are multiple boards. | 2 |
| 259 | JSW-6406 | The "View on Board" link for an epic does not take you to any scrum boards, despite the epic appearing in the Epic Panel in plan mode | Need to modify how this calculation is done so that the operation will offer to take users to Plan Mode. Q : Would the epic be selected? That could be strange as it would apply filtering. A : no, the epic is not selected (!) Testing Notes (!) Q: Make sure to be searching by an issue id, not epic name to prevent searching on duplicate names. A: (/) sure, searched by issue id Q: How performant is this across many boards, like JAC? A: (/) hard to say, but we basically added only one clause to the query. It shouldn't perform very differently from what is already deployed on JAC. Needs verification tough. Q: What if the Epics Panel is collapsed? A: (/) the panel is opened and the epic is selected. It means that issues that are not in the epic are filtered out Q: What if the user does not have permission to see a board/project that the Epic is involved with? A: (x) [~pobara], not sure how to produce this case, let's speak together about that | 3 |
| 260 | JSW-6432 | As a planner with a long backlog, I would like the Epics Panel to stalk the backlog as I scroll down | COS: - Need separate scrolling for long Epic lists (!) Testing Notes (!) Q: What happens if there are error messages in the page as well? A: (/) Error messages have an absolute position so they are not influenced by the epics pane. Q: How well does this work with all browsers? A: (/) Tested on IE8, IE9, last Firefox, last Safari and last Chrome. Q: What happens when the epics tab is very long and you scroll in it or in the main pane? A: (/) The epics pane has its own scrollbar, so when the content is longer than the available visible height, a scrollbar appears. Q: Try a combination of clicks and scrolls with epics/issues selected. A: (/) Bad behaviour when the view port is smaller than the minimum JIRA supported size, but it is normal. Q: What happens if the detail view is closed? A: (/) The epic pane is not influenced by the detail view. | 3 |
| 261 | JSW-6433 | As a planner, I would like a way to create new issues for an epic, so that the issues are automatically assigned to the epic | COS: - Issuetype should be their last issue type unless it was Epic in which case it should default to story - Use Quick Create - If they choose Epic let them create the Epic but don't do association (!) Testing Notes (!) Q: What happens if there is no Epic issuetype? A: (x) Not Answered Q: What happens after creating subtasks? A: (x) Not Answered Q: What happens after a Quick Edit, of an epic or story? A: (x) Not Answered Q: Is there an alert that will indicate to a user that the issuetype field has changed under them? A: (x) Not Answered Q: What if the issuetype field is not displayed on that screen? A: (x) Not Answered Q: What if it is restricted to a particular group? A: (x) Not Answered | 2 |
| 262 | JSW-6446 | Update selected epic treatment | spoke to Tokes about this this morning. See treatment at: https://extranet.atlassian.com/display/GHDEV/Epics+Selection+Scheme | 1 |
| 263 | GHS-6462 | Allow it to be possible to create a project at the same time as creating a board | COS: - After Scrum / Kanban choice allow (a) selection of existing projects (b) selection of a filter (c) creation of a new project - Link the Getting Started links in to this new dialog (with the appropriate selection, i.e. create sample kanban project goes to the second step of the dialog with 'Sample Data' selected) - Kill off "Advanced" | 5 |
| 264 | JSW-6462 | Allow it to be possible to create a project at the same time as creating a board | COS: - After Scrum / Kanban choice allow (a) selection of existing projects (b) selection of a filter (c) creation of a new project - Link the Getting Started links in to this new dialog (with the appropriate selection, i.e. create sample kanban project goes to the second step of the dialog with 'Sample Data' selected) - Kill off "Advanced" | 5 |
| 265 | JSW-6463 | Restore "Create Issue" dialog preferences after Epic is created | COS: - Also remember your 'All' or 'Custom' preference for fields - None of this applies to the Create Epic dialog (!) Testing Notes (!) Q: What happens if you switch modes or go to config before you create an issue? Aka how long do we queue up this memory? A: It's reset when the dialog is hidden. If you refresh the page with the dialog open, it doesn't get reset. Q: What happens if you edit an issue first, changing the fields that are shown there, then try quick create? A: Quick Edit and Quick Create customisation are independent. Q: What happens when you open the create dialog but then close it, and reopen again to actually create? A: (/) it's good | 2 |
| 266 | JSW-6466 | As a product owner, I'd like a days remaining in sprint gadget for the new boards (similar to the days remaining gadget) | # Same defaults when choosing the sprint as in GHS-6467 # Needs to take non-working days into account (we should make it explicit in the description of the gadget) # Mimic behaviour of classic version of the gadget otherwise # Wallboard compatible # Call it "Days Remaining in Sprint" gadget (!) Development Notes (!) Q: What happens if a user doesn't have permission to access a project in the gadget? A: (/) No permission error message? Q: Will the days remaining be calculated in the server timezone or adjusted to user timezone? (I think it would have to follow the server timezone to be accurate for remote teams) A: (/) User's timezone Q: Do the days remaining honor the time of day that the sprint ends? A: (/) Yes Q: What is displayed if there is no active sprint? A: (/) No active sprint error message Q: What is displayed if the sprint has been closed? A: (/) 0 Days Remaining | 3 |
| 267 | JSW-6467 | As a product owner, I'd like a burndown gadget for the new boards (similar to the existing Classic Burndown gadget) | - this is to mimic the behaviour of the burndown chart of the board # The sprint value can be chosen by the user. The default value is auto (the one that ends first) # No configuration to change estimation statistic # Needs to be wallboard compatible # Call it "Sprint Burndown" gadget (!) Development Notes (!) Q: Will Wallboard Mode be compatible for all supported browsers (IE specifically)? A: (/) Works but with some adjustments on IE8 (because of quirks mode) Q: What if a user does not have permission to see a project configured in the gadget? (either a single project or one out of multi-project board) A: (/) Will get an error message saying that the board can not be find Q: What if the sprint has run over its end-date? A: (/) Same as burndown chart Q: Does the y-axis adjust if there is scope addition? Do the tickmarks readjust? A: (/) Yes, thanks to flot Q: What if there is no active sprint? A: (/) Displays a message like "could not find an active sprint" Q: What if the active sprint has only issues that are in a project that the user does not have permission for? A: (/) Will get an error message saying that the board can not be find Q: Can the user hover over data points in the chart? A: (/) The user can't for now | 5 |
| 268 | JSW-6522 | As a user, I would like a confirmation when I delete a future sprint so that I don't accidentally lose all my work | The team I'm in had our 5 next sprints all planned out, which is something the Greenhopper planning UI somewhat encourages by saying "Plan some sprints". Somebody accidentally deleted the second one by hitting the subtle grey (x) in the top corner of the sprint. Re-adding it again is impossible. We have to rename all the sprints and shuffle the work down each one. Due to a single mis-click. If adding sprints to the middle is impossible, I suggest that deleting them from the middle also should be. | 2 |
| 269 | JSW-6537 | As a PO, I'd like to see the stories of an Epic in JIRA view issue | COS: - 'Issues in Epic' panel - Immediately beneath the sub tasks panel - Looks like the sub tasks panel -- No "Plus" button to create new issues -- No dropdown to filter issues -- No numbered list -- Prepend summary with issue key -- Fields: done-ness icon, issue key, summary, issue type icon, status, assignee -- Include issue operations cog per issue -- Order by "default" rank field - Don't show if there are no linked issues (!) Development Notes (!) Q: How does this perform with a large number issues? A: should be fine Q: What if you dont have permission to see some of the issues? Or not logged in? A: Only issues which the user has permission to see will be displayed in the list. Q: Any support or infrastructure for possible bulk edit functionality? A: No Q: View in issue nav link? A: No Q: What if there are non-stories with an epic link? Story was converted to something else? A: Any issue currently linked to the epic via the Epic Link field will be displayed. Q: What if epics have an epic link? (also converted from story) A: see above | 5 |
| 270 | JSW-6538 | As a PO, I'd like to see the Epic of a story in JIRA view issue | COS: - Show like the label - Can't remove it in the agile box (!) Development Notes (!) Q: Can you edit the value there? A: (/) No Q: Can you see this information as an anonymous user? A: (/) Yes | 1 |
| 271 | JSW-6539 | As a user, I would like to be able to associate an issue to an Epic from JIRA | Possible implementations: * Issue operation dialog * Field to edit with inline edit or Quick Edit | 5 |
| 272 | JSW-6594 | Clean up Epic-Issue link when changing the issue type of an issue | Epic -> Issue: Remove the epic link for all issues linked to that epic Issue -> Epic: Remove epic link if was previously part of an Epic Issue -> Subtask: Remove epic link to Epic if was linked Subtask -> Issue: If old issue parent had epic then link issue to epic (to be discussed if we really want this), unless the new issue type is Epic We shouldn't have to clean up epic label and epic color fields as these are only applicable to epics and therefore will automatically be cleared. (!) Testing Notes (!) Q: Make sure this plays well with the change to Epic Name field. A: The two are completely unrelated Q: What if subtasks are disabled either before or after trying to convert? A: (/) Can't disable sub-tasks while there are sub-tasks in the system. Q: Don't forget to add the Epic Link to the subtask if the parent has one. A: Epics are always only linked to parent issues, not to subtasks | 5 |
| 273 | JSW-6615 | Be able to query Epic assignment history of all issues ever assigned with an Epic | COS: - For a given epic return the history of all issues added and removed (with time) from the Epic - Will need to inform admins that they need to re-index - This does not involve the addition of JQL to assist in this querying (!) Development Notes (!) Q: I'm assuming this will only be seen on the view issue page? A: It won't be seen in the UI anywhere. It will only be seen by accessing the URL directly. Q: What if the epic has been deleted? A: You get an error message: issue does not exist. Q: What if the epic was converted to an issue/subtask? A: It doesn't check. If you changed it in JIRA and there are still epic child links, you'll still see the data. Q: What if the linked issue was moved/converted/deleted? A: It should still show up in the appropriate group (incomplete, complete, punted) Q: From what version forward will we be tracking this history? aka if an epic link already existed before we introduce this change? A: previous epic links should be tracked Q: Do any of these questions surprise you? If so, what hadn't you previously considered? A: the first one, because it's not a UI story Q: What else can you think of? A: (x) Not Answered | 5 |
| 274 | JSW-6616 | Show table at bottom of single Epic report that shows the estimate (current) for Done, Undone - Estimated, and Undone - Not Estimated stories | COS: - Similar to existing Sprint Report - Include key, summary and current estimate (!) Testing Notes (!) Q: What if issues are removed and readded to an epic? A: the report represents current state only Q: What happens to the table if there are negative estimates? A: same thing as sprint report Q: What if the epic is visible on the board, does not contain any issues on that board, but contains issues from another project? What will be displayed in the table? A: no issues - report is dependent on the board query Q: What if the estimation config is removed/modified from issues on the board? A: report represents current estimation config as per sprint report | 3 |
| 275 | JSW-6629 | Remove Epics from Labs | COS: - Remove admin option - Welcome mat changes (remove the banner) - Create Epic fields on startup (!) Testing Notes (!) Q: Make sure THE UPGRADE works both when Epics are PREVIOUSLY not enabled and are enabled. A: Tested empty upgrade with different JIRA versions as well as upgrading on different JIRA versions Q: Make sure Epics that are in the backlog of plan mode move properly to the sidebar and colored lozenges populate properly. A: The Epics move as expected but the colours + Epic Name will be empty as not yet set | 3 |
| 276 | JSW-6636 | As a user, I'd like to see change history for my Epic in the history tab for the Epic | COS: - Show change history every time a new issue is attached or detached from the Epic - When multiple issues are attached to an epic at once log just one change history entry - When multiple issues are detached from an epic at once log just one change - Can't use the Epic Link field (because that's always from Child to Parent) (!) Testing Notes (!) Q: Which events are tracked in the history? Are there any special events for issues that are either not tracked or different for epics? A: Just adding / removing issues, no special events. Q: Can you backdate changes? A: No Q: What happens to the change history for completing an epic and reopening it? A: History of added / removed issues shouldn't be affected. Q: What happens to the change history when estimating stories in that epic? A: Nothing | 3 |
| 277 | JSW-6665 | Put 'Filtered' icon at top of backlog and in each sprint header, clicking it clears all filters | For active sprints, upcoming sprints and the backlog we currently we only show a message inside the container when its contents are affected by a filter and no issues remain. The filter can be one or more of Instant Filter, Quick Filter(s), Epic Filter. For the sprints there are counts showing visible issues e.g. 3/11 Visible Issues, but not for the backlog. To help users realise there are filters affecting the contents of each container and assist with the removal of any filtering we will add an icon to any filtered container. The title attribute (tooltip) will contain a message in the format "32 Issues filtered. Click to clear all filters." Clicking the icon will reset all filters on the board including all Quick Filters, Epic Filters and the Instant Filter. If the Instant Filter was active then its contents would be removed as it is reset. *Stretch* Additionally while we are making the issue count available to the backlog container we will show the current issue count on the backlog header. See linked EAC page for sketch. --- (!) Testing Notes (!) Q: What happens when you apply instant filters? Is the field cleared as well? A: (x) Needs to clear value Q: What happens if you have issues selected? A: (x) Should not change selection Q: What happens to any open dropdowns when this button is clicked? A: (x) Not Answered Q: Do these buttons only clear filters for 1 sprint, or all? If not all, how would we display which filters are active for which sprints? A: (x) Needs to be for all Q: What if Epic filters are on but the panel is closed? A: (x) Needs to clear epic filter | 2 |
| 278 | JSW-6666 | Change Epic Label field to Epic Name | COS: - Rename any existing instances of the field to Epic Name - Rename the type of the field to Epic Name - Ignore any change items that were previously created against this field - Search for any references to "Epic Label" and replace them with "Epic Name" -- including documentation (cc: [~rosie@atlassian.com]) (!) Testing Notes (!) Q: What if there is a duplicate named field? A: (x) This could cause unexpected results but [~miruflin] states we can't do much about this. Deemed unlikely and an extreme edge case. Q: What if there is a field type for this already in the system? A: (x) This could cause unexpected results but [~miruflin] states we can't do much about this. Deemed unlikely and an extreme edge case. Q: What about existing quick filters or swimlanes (any JQL) that reference the field name? A: (x) JQL will become invalid, same as any JQL made on a field where the name is changed. Swimlanes/QF would be using Epic Link though since the parent's value is not available. | 1 |
| 279 | JSW-6709 | As a user, I would like to be able to find out more information about an issue's epic when the epic is "Done" | With the ability to mark epics as Done, it is now possible that users will see an Epic Name lozenge in the Backlog and not be able to see the epic in the panel that this name refers to. The lozenge on the Issue Detail View should contain a link to the epic's Epic Report. | 1 |
| 280 | JSW-6828 | As a Classic user I would like my epic-issue relationships migrated for use on the new boards | COS: - manually triggered for a whole project - show the number of issues to be updated before you hit go - make it clear that this only migrates data that exists right now - it does not synchronise the relationships over time. also make it clear that it can be re-run at a later time if necessary. - put in the global config in a new tab -- *Classic Epic Migration* - explain what is about to happen when they proceed: -- find issues with an issue key in the 'Epic / Theme' field then convert this to an Epic link. If a story is already linked with Epic Link field, ignore it. -- server-side logging - notify the Admin on confirmation page they should remove the Epic / Theme field (if it is no longer being used) - modify description of Epic/Theme custom field so that it references Classic Boards (!) Development Notes (!) Q: Need to try with data from epics still in labs A: (x) Not Answered Q: What happens when editing the old epic links? A: (/) The old epic links can be updated but are not synced to the new style of epic link. Another migration is needed to port over the updated classic epic link (this will only work if the target issue has not yet been linked to a new style epic link) Q: If you update classic epic links, will new ones be created as well from now on? A: (/) No, there is no synchronization between old and new epic links Q: What if there is old epic label data from when epics was still in labs (aka field is named something else)? A: (/) Upgrade tasks will have migrated it. The migration uses the configuration of classic mode to find the classic epic link custom field Q: Are there any differences with JIRA/AO versions we need to be wary of? A: (/) Nope | 8 |
| 281 | JSW-6905 | On plan mode rank newly created items immediately below the currently selected item | If issues are selected: - Ranked after the last selected issue If no issues are selected: - Ranked before the top visible issue, where "visible" means the section of the Backlog visible in the viewport (including upcoming sprints but not the current sprint) - If the current sprint is taking up the entire viewport, then the top of the backlog/future sprints is used If multiple issues are created at once: - Ranked in order of creation (as normal), all issues appear in the appropriate position based on the above rules. Filtering of any kind (Quick, Instant, Epic) should not impact on where issues are placed - the rules of visibility still apply. (!) Testing Notes (!) Q: What if the view is stale? A: We will place the issue according to the currently visible issues, so if they are out of date the issue might appear at the wrong place Q: What if the viewport is huge or very very small? A: Same result as if the viewport is normally sized. Q: What if the detail view is closed/open? A: doesn't affect the logic Q: What if multiple issues are selected? A: We'll place the issue after the last selected issue Q: What if an epic is selected? A: We currently don't have epic selection Q: What if a quick/instant filter is applied? A: See first answer, we'll place it before the first visible issue. In case the selected issue is instant filtered, we still place it after the selected issue Q: What if your last selected issue is the last issue but it was moved/deleted? A: moved: it will be ranked according to the new location. deleted: bad luck, it will be ranked last Q: Can you fool GH by setting the URL without loading it and creating at the new selection? A: no, GH doesn't look at the url, it looks at the internal state (which might come from the url when you hit return in the address bar). Even if it did, this wouldn't be the end of the world. Q: What if you don't have schedule permission? A: We'll silently ignore rank errors, so the issue will end up at the end of the backlog Q: What if the selection is within an active sprint? A: The issue would be added at the top of the backlog Answers provided by Michael R and Nikolay | 2 |
| 282 | GHS-6992 | Align project creation dialog to JIRA style | There are some differences in our project creation dialog to the JIRA one. * Remove "Project" from "Name" and "Key" field labels * Standardise on field descriptions for Name and Key (maximum length) ** Enforce maximum lengths on those fields | 1 |
| 283 | JSW-6992 | Align project creation dialog to JIRA style | There are some differences in our project creation dialog to the JIRA one. * Remove "Project" from "Name" and "Key" field labels * Standardise on field descriptions for Name and Key (maximum length) ** Enforce maximum lengths on those fields | 1 |
| 284 | JSW-7043 | GH code fixes required for latest 6.0-breakit version | In 6.0-breakit-SNAPSHOT since Jan 3rd, last unaffected version is 6.0-m04, ActionUtil, ActionNames, possibly ActionDispatcher and other related code has been removed. GreenHopper uses this code in classic board fields to update field values, e.g. set the assignee, component, version etc. To fix it, we'll have to replace all update code to use proper JIRA api. See the deprecated messages in ActionNames on what to replace the code with. | 5 |
| 285 | JSW-7159 | As Patrick, I want to see list of versions when I'm looking at the backlog | Considered versions: - versions which are BOTH: -- part of projects included in the board, AND -- unreleased -- not archived Ordering: - version sequence for versions within the same project (oldest first) - overall projects are ordered by project name Display: - version name along with project key (name on mouse hover) -- version name wraps around project key, if one or both are long - if the board only has one project, omit project name If there are no release versions you get an empty column. In the filters story we'll add an "all releases" button so it doesn't look so empty. (!) Development Notes (!) Q: What if there are duplicate version names? A: They look the same. Q: What if the version names are long? A: They wrap. Q: What if a version has been renamed / deleted in the system? A: It doesn't show up (archived versions dont' show up). Q: When reordering versions, are they bound to their container? A: The order can't be changed on this page. Q: What can I edit about the versions? A: Nothing. Nada. Rien. Nope. Q: What does the detail view display if a version is selected but no issues are selected? A: There is no selection of a version yet, that's part of the filter story. Q: What if the fixVersions field doesn't exist? A: (x) Not Answered Q: Is there a way to select another version field to be displayed here? A: (x) Not Answered Q: What if the version is "Archived" in JIRA? A: It isn't included in the list. | 5 |
| 286 | JSW-7160 | As Patrick, I want to be able to see more details about the version when looking at the Versions Panel | - this refers to the version panel - the behaviour should mimic the epic panel, including the twixies - information needed: description, start date, release date as well as count of total, completed and unestimated stories, total estimate units, small progress bar (startDate is not part of the progress calculation) - for empty data (release date, start date) reuse the same approach as we use on the detail view | 5 |
| 287 | JSW-7161 | As Patrick, I want to be able to create a new version | # Dialog is shown # fields we need to populate: Project, Name, Description, Release Date # Single Select (with autocomplete aka Frother) Control for project selection # Description field - text field # Apply sensible length limits to these input fields (check what limits JIRA has in place if any or just enforce a limit of 255 chars on the front end) # create version affordance is only displayed if the user has project admin permissions to at least one project (it is the same as can manage sprint logic) # Analytics to track usage of dialog #* Also capture length of version names (!) Development Notes (!) Q: XSS safe? A: (/) yes Q: What if the version name already exists? A: (/) We show an error message | 3 |
| 288 | GHS-7162 | As Patrick, I want to be able to delete a version | - allow for a version to be deleted - warn if other issues are assigned to it already - what permissions do we need for that action (TODO: team input here) | 3 |
| 289 | JSW-7162 | As Patrick, I want to be able to delete a version | - allow for a version to be deleted - warn if other issues are assigned to it already - what permissions do we need for that action (TODO: team input here) | 3 |
| 290 | JSW-7163 | As Patrick, I want to be able to edit details of a version | https://extranet.atlassian.com/display/GHDEV/GHS-7163+Versions+Inline+Edit | 5 |
| 291 | GHS-7164 | As Patrick, I want to choose a colour for a version so I can identify it easier in the backlog | - the general idea is for this to mimic the epic functionality | 5 |
| 292 | JSW-7164 | As Patrick, I want to choose a colour for a version so I can identify it easier in the backlog | - the general idea is for this to mimic the epic functionality | 5 |
| 293 | JSW-7165 | As Patrick, I want to assign issues to a version | - permissions - only one version can be associated with an issue (using this feature): fixVersion is replaced - can assign multiple issues to a single version easily - what happens when multiple issues from multiple projects are dragged? -- don't allow drop on version panel -- possibly explore additional message or change cursor - what happens when an issue from PROJA is dropped onto PROJB? -- don't allow drop on version panel -- show message - able to drag issues from active sprints or future sprints or backlog -- refer to comments below re: dialog when destructively updating Note: * IE8 experience may not be as good due to bad drag and drop performance * consider messaging for invalid drop targets (!) Development Notes (!) Q: What if the version list is stale and a version doesn't exist anymore/was archived? A: (/) We show a "Issue doesn't exist" message and we reload the issues list Q: What if an issue was converted to a subtask or epic? A: (/) We attach it anyway Q: What if the issue is already part of a sprint? A: (/) We allow it Q: Need to make sure the issue is not reranked if drop on version fails. A: (/) We always cancel ranking after drop on versions even if it fails Q: What if a group of issues is dropped but one or more fail to be added? What happens to the rest and how do we notify the user? A: (/) We don't update anything and we show a message saying that the user doesn't have the permission to update the issue(s) Q: Are the dropzones properly hidden when the version tab is hidden? A: (/) yes Q: Does drag and drop work well if quick and/or instant filters are on? A: (/) yes, no direct influence | 3 |
| 294 | JSW-7166 | As Patrick, I want to see the version assigned to an issue in the list view so I can quickly identify which issues belong to which versions | * Estimate column spacing still honoured * If there is no epic associated, version lozenge will be right-justified next to estimate * All version lozenges use the same colour, which is not a colour available to epics * Truncation assessed by the width (similar to epic lozenges) * What happens when an issue is associated with multiple fix versions through JIRA? ** Show somehow that there's more than one version on the lozenge ** The primary version is the first unreleased version in the sequence * Released versions are displayed * Archived versions are not (!) Development Notes (!) Q: What if the version name is very long? A: it's truncated (via CSS - martin to review) Q: Shouldn't the primary version in a multi-version be the soonest version, rather than the alphabetical one? A: (x) it's currently ordered alphabetically, please talk to Tokes / Tom if you think it should be different Q: How does this play with the epics / DV being open / closed? A: not affected Q: How do you remove an issue from a single version if it has multiple? A: you can't remove a fix version at all Q: What if one of the versions is / has been released? A: it still shows up Q: What if the version is "Archived" in JIRA? A: (x) Not Answered | 2 |
| 295 | JSW-7168 | As Patrick, I want to be able to filter my backlog to a specific version so I can easily see which stories will be included | * Includes adding "All issues" option for versions AND epics * Includes adding "Issues without version" option * Single version selection * Selected version for filter should be remembered in the URL * Epic numbers metadata will not be updated when filtering is active * If an epic filter is active, and then a version filter is activated which excludes that epic, the epic filter will revert back to "All issues" option (!) Development Notes (!) Q: So shift or control click do not work for multiple select? A: (x) Not Answered Q: What if a quick filter applies a version filter? A: (x) Not Answered Q: What if an instant filter is active? A: (x) Not Answered Q: Do we want to link the order of versions to the order of issues in the backlog? A: (x) Not Answered Q: What if an epic is selected and a version which is empty is selected? Do we still drop all the issues from the filter the same way if issues in the epic aren't in the version? A: (x) Not Answered Q: Does the instant filter only filter on the subfiltered issues, or on the entire backlog? A: (x) Not Answered Q: What is the hierarchy about how filters are applied now? A: (x) Not Answered | 5 |
| 296 | GHS-7170 | As Patrick, I want to be able to filter my backlog to a select few versions so I can see which stories will be included in them | NULL | 3 |
| 297 | JSW-7170 | As Patrick, I want to be able to filter my backlog to a select few versions so I can see which stories will be included in them | NULL | 3 |
| 298 | JSW-7171 | As Patrick, I want to understand the progress towards a version with a single report | - the chart needs to show the complete history of a version (incl scope changes) - it's a burnup chart showing total estimate vs complete estimate, total vs unestimated stories - also display count of unestimated stories - start date is defined as the day when first story from that version was added to the version (to use startDate once we have it) - also display the list of stories split into complete, incomplete, incomplete unestimated (we may want to consider adding full history later on); - each story on the list should display the epic it belongs to (!) Development Notes (!) Q: How does the chart look if it has been archived then unarchived again? A: the same Q: What if an issue is a part of multiple versions? Are there any implications for which version it is displayed in/ permission issues if this issue is in another project our user has no permissions to see? A: it's displayed in all of them if the user has permissions to see it Q: What if epics are in a version, how are they counted and displayed? A: They are added to the issue count and will show up in the table. Q: What happens to the chart when the first issue added to the version is deleted/moved/converted? A: it should show issue removed | 5 |
| 299 | GHS-7172 | As Patrick, I want to adjust release report projections to simulate and better understand what can be achieved within a version | - allow the percentage calculation to be adjusted (default to 10%) | 13 |
| 300 | JSW-7172 | As Patrick, I want to adjust release report projections to simulate and better understand what can be achieved within a version | - allow the percentage calculation to be adjusted (default to 10%) | 13 |
| 301 | JSW-7254 | As a user, I would like to create an issue inside an epic when viewing an epic in JIRA | The sub-task panel has a 'Create' button to create sub-tasks quickly for an issue. It would be good to have a similar mechanism when viewing an epic, so that you can create issues for the epic. (!) Development Notes (!) Q: How does this overwrite the current project and issuetype selection of the create issue dialog? A: (/) No overriding is done for the create issue dialog. It behaves identical to the normal dialog. Q: What happens if you open the create issue for epic and create issue dialogs one after the other? A: (/) Multiple issue creation is supported. After all issues are created and dialog is closed, then the created issues are associated with the epic Q: What if the epic is closed? A: (/) Issues will still be able to be associated to the epic. Q: What if the epic doesn't exist anymore? A: (/) An error message is shown saying the issue does not exist Q: What if the epic has been changed to another issuetype? A: (/) If the user is on the epic's view issue page and the epic's type is changed on another page, then creating issues in the epic work, but the association will fail with an error message saying the Issue should be of type Epic Q: What if you have inline edits open in jira before clicking the button? A: (/) They are closed before the dialog opens | 3 |
| 302 | JSW-7314 | Add Atlassian Analytics events to GH | All of the values below will need to be grouped by instance: - how many instances are actually activated (measurement: for every instance with GH enabled, make sure we store first visit to an instance - most likely to be /secure/Dashboard.jspa, which is in JIRA) - of these instances, how many find Rapid Boards (measurement: first visit to /secure/RapidStart.jspa in an instance) + how many of the ones without GH at first had them (this necessary to have the numbers right for the following points) -- Event is "gh.welcome.show" - how many attempt to create a project? (measurement: opening of the dialogue to create a project) -- Event: "gh.welcome.create.project.start" with type in "label" field - how many create a project + how many create a project of each type (scrum, kanban, diy) + how many create sample/non-sample projects? (measurement: store project_created as an event, with type associated to it, as well as if it was a sample project). -- Event: "gh.welcome.create.project.sampleData" with type in "label" field preceding the next event in case of simple data is used -- Event: "gh.welcome.create.project.complete" with type in "label" field - how many non-sample projects create a single issue (measurement: store issue_created event) -- Event: "gh.issue.created" with keys array stringified in "keys" field - of scrum non-sample users, how many create a sprint (measurement: sprint_created event) -- Event: "gh.rapidboard.sprint.backlog.addmarker" - of scrum non-sample users, how many start a sprint (measurement: sprint_started event) -- Event: "gh.start.sprint.dialog.change.start" when attempt to start the sprint -- Event: "gh.start.sprint.dialog.change.complete" when they actually start it + - how many users use rapid boards exclusively, how many use a mix, how many use classic exclusively - the first and last is what we cannot determine at the moment (measurement: store requests to RapidBoard.jspa vs the other two classic boards, then count these per week grouping by instance). Note that this is actual usage grouped instance, as opposed to usage overall (so larger instances having more influence) or binary on/off "has ever used a classic/rapid board" -- Event: "gh.rapidboard.show" on view of rapid board -- Event: "gh.classic.show" on view of classic board From Jay: - How many epics appear on a board -- Event "gh.rapidboard.epics" with "value" field as count - How many versions appear on a board -- TBD (!) Development Notes (!) Q: What if 1 action triggers more than 1 event? A: (/) It could and probably will - its up to the post-processing to effectively filter, order & group the events. | 5 |
| 303 | JSW-7357 | As an administrator, I would like to be able to turn on/off the Release Planning feature as a Labs Feature | * Surfaced in the GH Labs Configuration tab * Controls the visibility of any Release Planning feature/story | 1 |
| 304 | JSW-7358 | As a user, I would like for the Release Planning labs feature to be promoted on the Getting Started page | For administrators: this includes a button to enable the feature For non-admins: if not enabled, show a message saying it is available and they have to ask an administrator to enable it. Once enabled: show users a Feedback button. Admins also see a link to disable the feature. Jay to provide new icon. | 1 |
| 305 | JSW-7402 | As Patrick I'd like to be able to hide the versions panel | * State persisted in URL * Default view is Versions panel is collapsed * When both versions and epics panels are collapsed, show affordances that allow the user to differentiate between the two (!) Development Notes (!) Q: What if the detail view is not visible either? A: (x) Not Answered | 2 |
| 306 | JSW-7469 | Store startDate for fixVersion | As Patrick, I want to be able to specify a startDate for my fixVersion when creating it so that my charts can be displayed in a reasonable way. # allow to specify startDate when creating a version within GH # store as date with UTC timezone | 2 |
| 307 | JSW-7585 | document compatibility of GH with JIRA 6.0 (NB. dependent on Plugins 3) | NULL | 1 |
| 308 | JSW-7599 | As a user, I want to be able to create a GH board straight from the JIRA create project dialog so it's easier for me | This is about plugging into the plugin point exposed by JIRA and - specify the title - hijack the project post creation and redirect to GH - separate buttons for Scrum + Kanban - Simplified workflow by default without option to select (!) Development Notes (!) Q: Is there differing implementation between btf and OD that we need to consider? Application permissions? A: (/) I don't believe there should be any, these would relate to installation of GH when it's not present and will be dealt with in subsequent stories Q: What board configuration do we allow from this dialog? A: (/) This story only covers the minimum - the user will be able to specify project name, key and project lead (all of that provided by JIRA already), and we need to create a board for that project, assuming simplified workflow Q: What happens to our old create project+board dialog? A: (/) Nothing | 5 |
| 309 | JSW-7600 | As a BTF user, I want to be able to install GH via UPM when creating a project | This is to allow us to launch the UPM and install GH as the current dashboard process does. Further customisation of the process will be dealt with in a further story. Banner Text: "Please install GreenHopper" | 3 |
| 310 | JSW-7602 | As Patrick, I want to be able to see a projection of possible end date of a version | This is to be calculated using -an average time spent per completed story point (or any other estimation statistic)- average story points per day in a given release so far, plus optimistic and pessimistic variants by adding or subtracting -one standard deviation- 10% from it. (note this was changed because we already return data for story points completed by date but not time per story, and a standard deviation was too big of a difference in most cases and didn't seem to make sense) # The projections must be displayed somewhere outside of the chart as well. # Released versions do not need to show projections. # Show the intended release date on the chart (midnight end of the date specified). # Do not show calculations of velocity in the page. # Take NWD into account with the calculation of mean and SD. # Tooltips for potential targets show "type" (optimistic, pessimistic) and date. # At least 10% of total estimated work for the Version must be completed before projections are shown. (!) Development Notes (!) Q: What if users are using negative story points? A: If the predicted release date is in the past, we shouldn't display a prediction at all. Q: What if any of the rates approach infinity? A: We probably need to discuss with [~jrogers] [~mjopson] [~tkotecki] what is a good point to cut off. At the moment, if the predicted date is infinity, we don't display a prediction. If the most pessimistic date is infinity, we display a flat line and cut the chart off after the predicted date. But as long as it's not infinity, we display it. Q: What distinguishes a rate that approaches vertical from the scope change events that ARE vertical? A: (x) Not Answered (Don't really understand this question) Q: What happens when users change the estimation of their board, or remove it completely? A: The board will reflect the current estimation. Q: What if the estimation uses time tracking? Will we calculate deviation in minutes, hours, days? How will this be reflected on the axis? A: We will calculate units (of estimation) completed per day and use this to project. The axis won't change from what is displayed now: X is time and Y is estimation units. Q: What if the user is tracking work with Logged Work? Should this rate also be displayed? A: (x) Not Answered (do you mean time tracking?) Q: What do we display if a projected line goes significantly into the future before it touches the scope line? Potentially this could be years into the future, but this isn't realistic to display. A: The chart expands to display the most pessimistic date, unless it's infinity, in which case it expands to show the middle prediction. It could be years. Q: What happens to the lines if the version has been released? A: If the version is marked as released or if total scope = total completed scope then we shouldn't display a prediction. Q: What happens to the lines if the "predicted" release date is moved to the past? A: This should never happen. Q: What happens if the release date is moved into the future? A: Marking a version as released is separate from displaying a release date. Regardless of whether a release date is assigned, we will try to predict a date if total scope > completed scope and the version is not marked as released in JIRA. Q: What if the release date is removed? A: See above. Q: What happens to the projected lines if issues are removed from the version (resulting in scope change) or deleted entirely (resulting in chart change without history)? A: The scope line stays horizontal so if scope is removed then it moves down and in theory the release date should move forward. If the story was completed before it was removed then it's used in the calculation of average points completed per day. | 5 |
| 311 | JSW-7695 | As Patrick, I want the list of epics to reflect the current version filter | * When a version filter is active, the epics which are not part of that version (by way of issues) are shown as "faded out" ** These faded out epics will still be interactive (drag and drop, filter toggling) * Epic numbers metadata may be updated when filtering is active * If an epic filter is active, and then a version filter is activated which excludes that epic, the epic filter will revert back to "All issues" option * If a version filter is active, and a epic filtered for a an epic which has no issues in the currently selected version is selected, both filters are active and no results are shown (!) Development Notes (!) Q: Are there still drop zones for faded epics? A: (/) Yes Q: Will the epic unfade immediately if an issue is added? A: (/) Yes Q: Will the epic fade immediately when an issue is removed from it? A: (/) Yes Q: What happens if a quickfilter filters out all issues that are part of an epic? A: (/) There will be no impact on the fading of the epics Q: What if the instant filter is used? A: (/) There will be no impact on the fading of the epics Q: What happens when you "Create an issue in epic" for a faded epic? A: (/) If the created issue has the fix version of the version being filtered, the epic will be unfaded because now it contains an issue with the correct version Q: What happens if you create a new epic with a version selected? Is it born faded? A: (/) It will be fade-born yes Q: Do all faded epics unfade if you click the funnel? A: (/) Yes Q: Can you still modify faded epics through their dropdowns? A: (/) Yes Q: For all the files being touched, which other dependencies might be affected by changes? A: (/) No impact on other files/components | 5 |
| 312 | JSW-7700 | Bring context menu to work mode | - allow for multiple select (with current limitations) actions: - bulk change - open in issue nav - remove from sprint (& show the same warning as elsewhere) (!) Development Notes (!) (x) Check Interoperability with other actions on the board (while menu open, try ranking, transition, cog menu, etc) (x) Check permissions to remove from spint, bulkchange (non-admin, user without delete permission, etc) (x) Check right-click does not trigger where it shouldn't (issue in done then open detail view) (x) Scrolling - should disappear when context changes (x) Stale state - what if an issue was already removed from sprint? (need 2 users) (x) Check with various board configurations (swimlanes, kanban with releasing) | 3 |
| 313 | JSW-7753 | Swimlane by epic | As Patrick, I want to use epics for swimlanes so I can see progress of each epic within a sprint more easily. # Both stories and subtasks for the epics should display. # Only an option for Scrum boards # The swimlane presentation is similar to "story task" swimlane: Epic Name, possibly issue key # No detail view shown for epic; clicking on swimlane selects first issue in swimlane (same as Assignee) # Issues without epics shows at the bottom | 3 |
| 314 | JSW-7805 | Display a invalid drop target icon on the version list when trying to assign story for a different project to a version | Use the browser default cursor "not allowed" | 2 |
| 315 | JSW-7842 | Integrate GH install via JIRA project template | The work for this is on a branch of the JIRA plugin (jira-project-templates-plugin) (!) Development Notes (!) Q: For each of the files you are modifying, what dependencies rely on or share the code you're changing? A: (x) Not Answered Q: What safeguards exist if the GH install fails or is incomplete? A: (/) That is handled by UPM, if GH is already installed, the installer shouldn't show because GH is providing it's own project templates Q: Do we have a dependency on UPM version for this to work? If so, do we have a check in place? A: (/) Dependency on JIRA 6.0+ and the UPM it uses. Q: How does licensing work? What if GH is unlicensed? Or if a license cannot be obtained from MAC? A: (/) If no evaluator license can be obtained, the installer will show an error and GH will be unlicensed. Q: What if a very old version of GH is already installed on the instance? A: (x) Not Answered | 3 |
| 316 | JSW-7874 | ADG GH: Resizable Detail View | - For this story, Plan Mode only - Idea is that we have a draggable left side for when people need more space, similar to other products (e.g. Confluence). - This drag would be remembered per client (local storage) in terms of percentage of window size - Consider what happens when DV is dragged too far - do other columns collapse or resize - Consider whether we do two-line issue representation for backlog column Testing notes below | 5 |
| 317 | JSW-7876 | Enable GH on OD instances from the Create Project dialog | COS The user will go through these steps: # Click to create a project # Select Scrum / Kanban # If GreenHopper is NOT installed, display an installation message tailored to the type of instance (BTF/OD) # For OnDemand, click a link to go to MAC and get the license # Once license is purchased, go to welcome page for GH with create project dialog open and scrum/kanban selected # If user cancels, return to previous page (can create project dialog be open?) # Add analytics events for every step as much as possible This should use the existing API as provided by the Internal Systems team (meaning we need to open a new page with MAC and they'll need to log in). # Copy to be provided. Note to self: make sure to include a warning that you need to be the account owner to enable it. Also that the trial only works if you haven't installed GH before (otherwise you'll be charged). Copy: https://extranet.atlassian.com/display/GHDEV/GHS-7876+OD+Create+Project+Sequence (!) Development Notes (!) Q: What if MAC is inaccessible? A: (x) Not Answered - I guess the user will get a 404 when they click the link. Q: What if a GH jar is present but not enabled? A: (x) Not Answered - if GH is not licensed, the message will display. | 3 |
| 318 | JSW-7983 | Edit startDate of a fixVersion in JIRA | As Patrick, I want to be able to edit startDate for a fixVersion in JIRA so that the experience between GH and JIRA is consistent and not confusing. h4. Approach for JIRA 6.0 JIRA code base: * Modify JIRA's {{version}} table to include a start date column * Make the above schema change on JIRA 5.2.x branch so that downgrades continue to work. * Augment the RESTful table in JIRA's Project Admin page for Versions to show this start date and allow editing of it * Augment the REST representation of versions to include start date * Add the start date field to the JIRA API for a Version object GH code base: * Make GH aware of the capability of storing start date in either JIRA or GH, depending on the JIRA version. * Migrate data stored in GH for start date to JIRA storage if available. (!) Development Notes (!) Q: How will adding a startDate to a previously released version affect the issues that apply to it? A: (/) If a previously released version has a release date, the new start date will be validated against the release date. Q: How will adding a startDate affect issues that have been Archived? A: (/) Changes to version data do not affect issues. Q: Which timezone setting will the startDate follow, user's or system's? A: (/) Start date and release date are both stored in the JVM system time zone. Q: Can you remove the startDate after adding it? A: (/) Yes. Q: What is one way to get the startDate to come after the releaseDate? A: (/) Not possible. Q: What happens when you add a startDate to a version that has been released but has no releaseDate? A: (/) Start date can be added without release date. Q: Is there a special place in the database this column/row will go? Depending on the database used, is there a way for this location to be already taken, and/or do we recycle a location/field ID? We need to protect against overwrites. A: (/) The field {{startdate}} did not exist in the table {{projectversion}} before now. Q: How is the data synchronised between GH AO tables and JIRA? A: (/) When the Version meta data is asked for in GH, it will check to see if it exists in JIRA as well. If so, it will be migrated over. | 8 |
| 319 | JSW-8014 | Display a trendline for version chart | As Patrick, I want to see a trendline on the version chart so I can understand how the projection works. A/C: # display the trendline connecting projection to start of the version # if some stories have been removed from the version *after* they have been completed, then the line won't match the projection and that's fine. Otherwise the trendline is a straight line. | 2 |
| 320 | JSW-8022 | Adjust the shading for epic & version report | # Use the same shades as Jay indicated in "Sexy charts" doc: https://extranet.atlassian.com/display/GHDEV/GHS-7825+Sexy+Chart # don't display the lines on the edge of the projection | 2 |
| 321 | JSW-8023 | Use the startDate in version report calculations | # include the startDate for calculations in Version Report - both in the description on the top as well as on the timeline (i.e. timeline starts on the startDate) # versions without startDate use the previous calculations # if some stories were completed before the startDate, the "completed" line is adjusted at start, but are not included in the trendline calculations, nor do we display time before startDate. Notes: - we might not be happy with the result and it may end up with the code staying on a branch + extra stories being created to improve it | 2 |
| 322 | JSW-8053 | As a user I want to be able to see the Epic Name as a column in Issue Navigator searches | Currently, using the Epic Link column only shows the epic's issue key. | 2 |
| 323 | JSW-8137 | Update the open/close epic/versions panel(s) | COS: Went through some variations on design before Martin suggested a 2-story-point fix for the story that is a slight deviation from the current design, but that a) pulls in hover-X to close version or epic panel b) when a panel is open, there is no left-side sideways text | 5 |
| 324 | JSW-8164 | Promote Release Planning out of labs | COS: # Remove the advertisement from Getting Started page # Remove labs flags in code | 1 |
| 325 | JSW-8408 | Excel export - plan mode | As Patrick, I want to be able to export selected stories to excel straight from GreenHopper so I can easily manipulate them the way I want. Notes: - this should use JIRA's "Export to Excel" feature, and respect its configuration - it should be available from the context menu | 3 |
| 326 | JSW-8450 | diagram of GreenHopper data / how it all works | Suggested by Matt Doar: https://confluence.atlassian.com/display/GH/GreenHopper+JIRA+Configuration?focusedCommentId=335479270#comment-335479270 e.g. see diagram on this page: https://confluence.atlassian.com/display/JIRA/Configuring+Fields+and+Screens | 3 |
| 327 | JSW-8469 | In order to be able to select report options easily, I want a better control to use | When opening a dropdown menu with a large amount of options, the menu doesn't force the page to scroll. CoS: # Four reports are affected: Version Report, Sprint Report, Sprint Burndown, Epic Report # Control uses auto-complete, single select style # No grouping of select options (!) Dev Notes (!) Q: Is the frother case-insensitive? A: yes Q: Does it search on spaces or any single char? A: Spaces no. Any character yes. Q: What happens when an invalid string is typed in? Can we do other actions? A: No Matches message, if you try to submit an invalid value it should revert to the previous selection Q: What happens when you search on closed/archived sprints/versions? A: same options show up as we had previously Q: Can you search as an anonymous user? A: same options show up as we had previously Q: Is the input XSS-safe? A: yes Q: How long can the input be? A: no limit, if it doesn't match then we revert to the selection Q: Are there tests to update? A: Epic and Version Report qunit tests are updated to reflect the changes | 3 |
| 328 | JSW-8471 | GH updates for JIRA 6.0 ADG changes (mainly Admin nav?) plus Gadgets | See https://extranet.atlassian.com/display/TECHWRITING/ADG+Changes+for+JIRA+6.0 Main functionality changes: * admin nav? GH docs to be updated: * *TO DO* https://confluence.atlassian.com/display/GH/GreenHopper+Administrator%27s+Guide *(CHILDREN)* * *TO DO* https://confluence.atlassian.com/display/GH/GreenHopper+Installation+and+Upgrade+Guide * *TO DO (WILL INHERIT MINOR PAGE CHANGES IN JIRA 6.0)* Gadgets - screenshots | 2 |
| 329 | JSW-8485 | Change "hide nav bar" shortcut | Currently it's 'z' to cycle between normal, projector and no-nav mode. Let's separate it so 'z' toggles projector mode only (as it used to), and Ctrl+Shift+F toggles the "hide nav bar" mode. Rationale: this is consistent with how Confluence does it, and also Google Docs. | 1 |
| 330 | JSW-8491 | Gather information about potential sprint conflicts | What we want to get out of it: - 1 for having gh - amount of rapid boards - amount of kanban boards - amount of scrum boards - amount of sprints - amount of issues in scrum boards - amount of issues which belong to multiple sprints - amount of sprints which contain said issues - 1 if this instance had problem | 3 |
| 331 | JSW-8623 | Write soke tests to measure UI performance on the plan mode | Scenarios to cover: - rerank within the backlog - add to an active sprint - add to an epic - add to a version - render the context menu (both for an issue that's already selected as well as one that's deselected) | 2 |
| 332 | JSW-8662 | Assign a story to future sprint | As Patrick I want to be able to assign a story to a future sprint so that it's query-able (via sprint id). A/C: 1. I am able to create future sprints which I can assign issues to 2. I'm able to remove future sprints and the issues are removed from them 3. I'm able to move issues between future sprints and out of future sprints and the db is updated accordingly 4. The backlog shows all future sprints, regardless of whether they are empty or not Notes: - as part of this, the necessary DB work to enable future sprints needs to happen (!) Dev Notes (!) h4. Functionality that changes: - Send to Top (from JIRA) - Sprint dragging will not include filtered issues Q: What happens if a sprint becomes orphaned aka all assigned boards are deleted? A: (x) Not Answered Q: What if the sprint's owning board was deleted but it was visible on a second board? A: (x) Not Answered Q: What if a non-visible orphaned sprint was included in the filter of a new board? Is it reassigned? A: (x) Not Answered Q: What if there are multiple rank fields? A: (x) Not Answered Q: Do sprints need their own rank field? If so, is it locked? What if it is deleted/modified in JIRA 5.1? A: (x) Not Answered Q: What are the conditions for the migration task? A: (x) Not Answered Q: What happens to sprints for which all issues have been deleted? A: (x) Not Answered Q: What if an issue is assigned to more than 1 future sprint via different boards? A: (x) Not Answered | 13 |
| 333 | JSW-8665 | Autocomplete for Epic Link in JQL | As Patrick, I want to be able to see autocomplete when querying Epic Link in JQL so that it's easy to write queries without making spelling mistakes. | 3 |
| 334 | JSW-8666 | Add an issue to an Epic from JIRA when no other issues have been added to it yet | As Patrick, I want to be able to add an issue to an empty epic when in JIRA so that I can fill it in easily. Notes: This can be achieved either via issue operation or always showing the existing "issues in epic" panel | 1 |
| 335 | JSW-8667 | Allow to set resolution in Simplified Workflow | As Patrick, I want to be able to specify which statuses transitions to which trigger the resolution field to be set to done so that my issues have any resolution at all. Solution 1. Allow for a tickbox per status, which makes the global transition to that status set the resolution to "Done". 2. Unmapped statuses will also display this information (not necessarily the option to change it) 3. During the conversion to simplified workflow, the user will be presented with the default choice of statuses from the "Done" column selected for the resolution but should be able to override it before finishing the conversion. Note that this will help people who are migrating as well as ones who have already migrated to simplified workflow. (!) Dev Notes (!) Q: Is this changed in GreenHopper Configuration? A: (/) Its board specific so its in board configuration. Q: How do we display the valid options as a part of the simplify dialog? A: (/) With a multi select combo box Q: How many statuses can you tick? A: (/) No Limit Q: What happens if the user moves a status to another column? A: (/) The column is moved, the tick is not changed Q: What if the user deletes a column that has a ticked box? A: (/) Just move all statuses to unmapped column Q: What if a status is dragged to unmapped? A: (/) Should be disabled but visible | 8 |
| 336 | GHS-8745 | Expose GH defaults as an API | Currently other plugins can't access GH defaults such as Epic Issue Type or default custom field ids, and as a result can't do stuff where this is information is needed. Add a new API that exposes this information to be consumable in java | 2 |
| 337 | JSW-8745 | Expose GH defaults as an API | Currently other plugins can't access GH defaults such as Epic Issue Type or default custom field ids, and as a result can't do stuff where this is information is needed. Add a new API that exposes this information to be consumable in java | 2 |
| 338 | JSW-8746 | GH further ADG updates | * *DONE* https://confluence.atlassian.com/display/GH/Configuring+a+Board *PLUS CHILDREN* * *DONE* https://confluence.atlassian.com/display/GH/Creating+a+Board * *POSTPONE UNTIL JIRA 6.0* https://confluence.atlassian.com/display/GH/GreenHopper+Administrator%27s+Guide *(CHILDREN)* * *POSTPONE UNTIL JIRA 6.0* https://confluence.atlassian.com/display/GH/GreenHopper+Installation+and+Upgrade+Guide | 2 |
| 339 | JSW-8942 | Flagging on stories as swimlanes in work mode | This needs to cover wallboards too. CoS: # Right click context menu should be available for parent issue swimlane ## The menu only contains one option which is to Add or Remove Flag (depending on state) ## Menu is only opened when right-clicking not on a control inside the swimlane (i.e. not on the issue key, not on the "transition", not on the twixie) # The option should be available via Cog menu (already present) # Flagged state needs to be visible in Wallboard Gadget (!) Dev Notes (!) Q: What if the JQL swimlane is defined as a single issue? A: You can't flag it Q: Does it work if the swimlane is collapsed/expanded? A: It still appears as flagged and you can still flag it. Q: Does it work in all supported browsers? A: yes | 2 |
| 340 | JSW-8974 | Wizard-like Create Board dialog | As Patrick, I want to be guided when creating a board so I don't get lost in the process. CoS: - The dialog consists of three parts: -- Board type (Scrum, Kanban) -- Project/Filter (create new project, choose existing, specify saved filter) -- leftovers: sample data on/off, workflow (JIRA vs GH Simplified) - this dialog replaces the existing ones present in: -- create new scrum board -- create new kanban board -- create new DIY board -- the dialog available from the cog menu (incl Manage Boards) - the "DIY" option is removed from the "Getting Started" screen as it is effectively obsolete - if Scrum or Kanban mode is chosen from the "Getting Started" screen, then the wizard should start at step 2 (i.e. we already know if it's scrum or kanban) - the text inviting you to create new project or choose existing on "Getting Started" needs rewording so it simply opens the dialog -- remove the two "1" and "2" things and replace with just "1". - the link to create a sample project should be rewired to use the new wizard and take you directly to creating the project with sample data and workflow options already selected. (!) Dev Notes (!) Q: What if there are no existing projects to select? A: Skip the step to choose and go straight to create new project Q: What if there are no filters to select from? A: No option to choose to create from a filter Q: What if the user has no permissions to create a project? A: menu link or button disabled; getting started text changes and does not show option to create Q: For OnDemand, what if the user doesn't have all application permissions to create a project? A: menu link or button disabled; getting started text changes and does not show option to create Q: What if there is a large number of existing projects? A: Drop down is really long Q: What if there are a large number of filters? A: Drop down is really long Q: What if the user does not have permission to see some/all filters? A: They won't appear in the list Q: Are selections persisted between board creations? A: No Q: Does scrolling through all the panes persist selections? A: Back / Next through pages should persist selections Q: Is there proper XSS escaping for filters and projects? A: Yes Q: What if the window is resized? A: Dialog stays the same size Q: Does the create button disable/spinner after pressed? A: There is a spinner. Q: What happens if the operation is cancelled after the create button is pressed? A: Within the process the dialog just goes away and no board is created. After the final button is pressed the page will reload and go to board, no cancel button. Q: Has this been checked from plan, work, and report? Manage Boards, Board Configuration, and Getting Started all the same? A: Link will be in menu for Manage Boards, Plan, Work and Report. Q: Will the dialog not render properly in some browsers? A: No, it will always be beautiful. A2: In JIRA 5.1, 5.2 the dialog has some differences as expected. | 8 |
| 341 | JSW-9132 | Update close icon in Detail View to be a font icon | NULL | 1 |
| 342 | JSW-9349 | In order to be better aware of the sprint markers migration, as an administrator I want to see a banner when GH 6.3 is installed | CoS: * Simple text banner communicating that this release contains migration and that administrators need to be aware of what's happening. * Link to Upgrade Notes/Migration docs * Appears on every JIRA page once only * Appears for every administrator user. * Needs to stack well with other potential banners that JIRA provides. * If the user installs GH for the first time and has no boards, or all the boards are already migrated, then we don't want to see this message. (!) Dev Notes (!) Q: Does the banner show up for every user, or just admins? A: (/) Just system et regular admins Q: Does it show only once, or does it persist? A: (/) Once Q: Does it still display if GreenHopper is unlicensed? A: (/) No Q: Does it display even with the redirect to Getting Started? A: (/) Yes Q: Does it display for anonymous users? A: (/) No | 2 |
| 343 | JSW-9488 | Change visual treatment on issue count in swimlane header to not use AUI badge | See attached screenshot. Should be 12px "Small text" from ADG: https://developer.atlassian.com/design/typography.html edit: currently there is no filtering treatment | 1 |
| 344 | GHS-9559 | Quick filters should collapse into a "... Show more" reveal pattern when they will wrap to more than one line | We should use a pattern similar to the Reveal text pattern from the ADG. * When there are more Quick Filters than there is horizontal screen space (eg. the screen is not wide enough, and they will wrap), we hide the remaining ones and display a "... Show more" link as the last Quick Filter. * Clicking "... Show more" will reveal the rest of the Quick Filters * "... Show more" will now change to say "Show less" instead * The default state for all users is the collapsed state * Whether the Filters are collapsed or all shown is persistent on a user level * Reordering the Quick Filters stays the same as it is today * When the header is collapsed (z on the keyboard), the behaviour stays the same. | 3 |
| 345 | JSW-9559 | Quick filters should collapse into a "... Show more" reveal pattern when they will wrap to more than one line | We should use a pattern similar to the Reveal text pattern from the ADG. * When there are more Quick Filters than there is horizontal screen space (eg. the screen is not wide enough, and they will wrap), we hide the remaining ones and display a "... Show more" link as the last Quick Filter. * Clicking "... Show more" will reveal the rest of the Quick Filters * "... Show more" will now change to say "Show less" instead * The default state for all users is the collapsed state * Whether the Filters are collapsed or all shown is persistent on a user level * Reordering the Quick Filters stays the same as it is today * When the header is collapsed (z on the keyboard), the behaviour stays the same. | 3 |
| 346 | JSW-14574 | Change activity stream documentation regarding repository commits | It is not clear in [the documentation for activity stream|https://confluence.atlassian.com/display/JIRA/Adding+the+Activity+Stream+Gadget] which commits from repositories in DVCS accounts are shown. It seems that only ones with smart commits linking to JIRA issues appear in activity stream. | 4 |
| 347 | JSW-14350 | As a writer I want to create multiple articles so that they can be published | NULL | 3 |
| 348 | JSW-14367 | As a reviewer to be able to review articles and add comments | NULL | 3 |
| 349 | JSW-14368 | As a reviewer I want to have an account so that i can review an article | NULL | 4 |
| 350 | JSW-14348 | As an Admin I want to be able to assign roles | NULL | 4 |
| 351 | JSW-14353 | As an Admin I want to create Writer accounts | NULL | 4 |
| 352 | JSW-14355 | As an Admin I want to create Reviewer accounts | NULL | 4 |
| 353 | JSW-14361 | As an Admin I want to create MediaManager accounts | NULL | 4 |