Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Reviews/R4E Reviews Stories"

(New page: ==Key== {{UserStory|(Name)|(Description)|(Bugs)|Estimate}} ==UI== ===Mylyn Connector Support=== {{UserStory |Mylyn Team Repository |User creates new repository connecting to a single R...)
 
 
Line 10: Line 10:
 
|Mylyn Team Repository
 
|Mylyn Team Repository
 
|User creates new repository connecting to a single Review Group. {{r4EDesign|Alternative_1:_1_Review_Group_.3D_1_Tasks_Repository}}
 
|User creates new repository connecting to a single Review Group. {{r4EDesign|Alternative_1:_1_Review_Group_.3D_1_Tasks_Repository}}
|{{Bug|389464}} {{Bug|389460}}
+
|{{BugN|389464}} {{BugN|389460}}
 
}}
 
}}
  
Line 16: Line 16:
 
|Mylyn Task List
 
|Mylyn Task List
 
|User can interact with existing R4E reviews using all standard task list functionality, just as they can with for example Gerrit reviews.
 
|User can interact with existing R4E reviews using all standard task list functionality, just as they can with for example Gerrit reviews.
|{{Bug|389458}}
+
|{{BugN|389458}}
 
}}
 
}}
  
Line 22: Line 22:
 
|Mylyn Task Editor
 
|Mylyn Task Editor
 
|User can create a new or edit an existing r4e review. The following items will be shown:
 
|User can create a new or edit an existing r4e review. The following items will be shown:
|{{Bug|389461}}
+
|{{BugN|389461}}
 
}}
 
}}
  
Line 28: Line 28:
 
|Mylyn Context Activation
 
|Mylyn Context Activation
 
|When user activates task, all of the typical context activation will work.
 
|When user activates task, all of the typical context activation will work.
|{{Bug|389463}}
+
|{{BugN|389463}}
 
}}
 
}}
  
Line 34: Line 34:
 
|Mylyn Task Scheduling
 
|Mylyn Task Scheduling
 
|User can schedule tasks as supported by generic Mylyn functionality.
 
|User can schedule tasks as supported by generic Mylyn functionality.
|{{Bug|389467}} {{Bug|389468}}
+
|{{BugN|389467}} {{BugN|389468}}
 
}}
 
}}
  
Line 47: Line 47:
 
#Summary/Name (Not in design discussion)
 
#Summary/Name (Not in design discussion)
 
#Date Range (Not in design discussion)
 
#Date Range (Not in design discussion)
|{{Bug|389462}}
+
|{{BugN|389462}}
 
}}
 
}}
  
Line 53: Line 53:
 
|R4E Due Dates
 
|R4E Due Dates
 
|User can enter and edit due dates using R4E views. Review due date is supported in R4E backing model.
 
|User can enter and edit due dates using R4E views. Review due date is supported in R4E backing model.
|{{Bug|389468}}
+
|{{BugN|389468}}
 
|Complete
 
|Complete
 
}}
 
}}
Line 62: Line 62:
 
|Common Navigator Infrastructure
 
|Common Navigator Infrastructure
 
|(Infrastructure) Content providers, label providers and other constructs are defined for reviews, comments, artifacts and people.
 
|(Infrastructure) Content providers, label providers and other constructs are defined for reviews, comments, artifacts and people.
|{{Bug|334967}}
+
|{{BugN|334967}}
 
}}
 
}}
  
Line 68: Line 68:
 
|Review Perspective
 
|Review Perspective
 
|User is provided with a custom perspective that opens the appropriate custom views and organizes the workbench for an effective review process. (Not in SOW, but a relatively easy, nice feature to have.)  
 
|User is provided with a custom perspective that opens the appropriate custom views and organizes the workbench for an effective review process. (Not in SOW, but a relatively easy, nice feature to have.)  
|{{Bug|390372}}
+
|{{BugN|390372}}
 
}}
 
}}
  
Line 74: Line 74:
 
|Artifacts View
 
|Artifacts View
 
|User can view artifacts associated with a specific review in a custom view. The view always displays artifacts for the given view. When users double-click an item in the view, a compare editor is revealed with the items. (When no review is active, a hint is displayed.) We way also support listing related comments as children here.  
 
|User can view artifacts associated with a specific review in a custom view. The view always displays artifacts for the given view. When users double-click an item in the view, a compare editor is revealed with the items. (When no review is active, a hint is displayed.) We way also support listing related comments as children here.  
|{{Bug|390369}}
+
|{{BugN|390369}}
 
}}
 
}}
  
Line 83: Line 83:
 
#Display items that are associated with the currently selected appropriate parent. For example, if a Review is foregrounded all comments for that review will be depicted. If a Java class editor is active, comments for that java class will be displayed.  
 
#Display items that are associated with the currently selected appropriate parent. For example, if a Review is foregrounded all comments for that review will be depicted. If a Java class editor is active, comments for that java class will be displayed.  
 
#As we are using common navigator, it would be simple enough to use both! That is, provide some toolbar item to allow users to see all comments or filtered comments.
 
#As we are using common navigator, it would be simple enough to use both! That is, provide some toolbar item to allow users to see all comments or filtered comments.
|{{Bug|390371}}
+
|{{BugN|390371}}
 
}}
 
}}
  
Line 89: Line 89:
 
|Participants View
 
|Participants View
 
|Users can see all people associated with a given review, including assignees and commentators. UI cues are provided so that users can easily determine participant role. Users are able to easily add additional participants.
 
|Users can see all people associated with a given review, including assignees and commentators. UI cues are provided so that users can easily determine participant role. Users are able to easily add additional participants.
|{{Bug|390375}}
+
|{{BugN|390375}}
 
}}
 
}}
  
Line 101: Line 101:
 
|Participants Auto-Complete
 
|Participants Auto-Complete
 
|In any UI element in which a User adds a particpant, the user is provided with auto-completion suggestions.
 
|In any UI element in which a User adds a particpant, the user is provided with auto-completion suggestions.
|{{Bug|390377}}
+
|{{BugN|390377}}
 
}}
 
}}
  
Line 107: Line 107:
 
|Comment Spellcheck
 
|Comment Spellcheck
 
|User can spell check their review comments. This must include support for r4E anomalies.
 
|User can spell check their review comments. This must include support for r4E anomalies.
|{{Bug|344100}}
+
|{{BugN|344100}}
 
}}
 
}}
  
Line 113: Line 113:
 
|Comment Replies
 
|Comment Replies
 
|User can reply to reviews. This must include support for r4E anomalies.
 
|User can reply to reviews. This must include support for r4E anomalies.
|{{Bug|344108}}
+
|{{BugN|344108}}
 
}}
 
}}
  
Line 119: Line 119:
 
|Comment Wikitext
 
|Comment Wikitext
 
|User can edit comments using Mylyn wikitext support.
 
|User can edit comments using Mylyn wikitext support.
|{{Bug|390374}}
+
|{{BugN|390374}}
 
}}
 
}}
  
Line 139: Line 139:
 
#The R4E ecore model may be refactored and modified to better support EMF idioms.
 
#The R4E ecore model may be refactored and modified to better support EMF idioms.
 
#The R4E genmodel will be modified to support EMF idioms and additional code generation capabilities. As part of this task, we may also generate the EMF Edit code we're likely to need later.
 
#The R4E genmodel will be modified to support EMF idioms and additional code generation capabilities. As part of this task, we may also generate the EMF Edit code we're likely to need later.
#We will not be able to preserve back-ward compatibility for existing R4E models. See {{Bug|390065}}.   
+
#We will not be able to preserve back-ward compatibility for existing R4E models. See {{BugN|390065}}.   
 
#All usages (e.g. Java API, resource managers...) of the Reviews or R4E model will be updated to support the new generated model.   
 
#All usages (e.g. Java API, resource managers...) of the Reviews or R4E model will be updated to support the new generated model.   
|{{Bug|324327}}
+
|{{BugN|324327}}
 
|In Progress
 
|In Progress
 
}}
 
}}
Line 148: Line 148:
 
|Model Notifications
 
|Model Notifications
 
|When an R4E resource is saved on its host file system, Mylyn tools are notified of new dirty status so that they can request an update.
 
|When an R4E resource is saved on its host file system, Mylyn tools are notified of new dirty status so that they can request an update.
|{{Bug|389465}} {{Bug|389466}}
+
|{{BugN|389465}} {{BugN|389466}}
 
}}
 
}}
  

Latest revision as of 16:55, 25 September 2012

Key

{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}

UI

Mylyn Connector Support

{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}
{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}
{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}
{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}
{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}
{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}
{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}

Reviews UI Improvements

{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}
{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}
{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}
{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}
{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}
{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}
{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}
{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}
{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}
{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}
{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}

Core

{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}
{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}
{{{name}}}
{{{text}}}
[[#{{{name}}} Plan|Plan]] {{{bugs}}}

Back to the top