Menu ▾ ▴

Feature Requests  Maximize  Restore

========================
States of a Change Request.
========================

-Hasn't been looked at. (Represented on sourceforge as Status:Open Resolution:None)
This means that the request hasn't been looked at and is still considered new.

-Reviewer requesting more info (Represented on sourceforge as Status:Pending Resolution:None)
This means that the reviewer has read the request and is requesting a
clarification

-Approved but not completed (Represented on sourceforge as Status:Pending Resolution:accepted)
This is a green light from the technical committee to move ahead with
development

-Deferred to tech group. (Represented on sourceforge as Status:Pending Resolution:remind)
This means the request has been scheduled for review at the next Technical
Committee meeting.

-Need more info. (Represented on sourceforge as Status:Pending Resolution:postponed)
This means the Techincal Committee has reviewed the request and is requesting
more information about the change.

-Approved and completed (Represented on sourceforge as Status:Closed Resolution:fixed)
This status means the code has been committed to the repository and has been
approved to be included in the next release

-Rejected (Represented on sourceforge as Status:Deleted Resolution:rejected,invalid,out of date)
This status means the change request has been rejected.

========================
Usage
========================
Assignment : tasks are assigned by developers to themselves when they are
ready to work on the item.

Group : When a feature is submitted to gerrit, the group field should be set
to release it is for, i.e. the next release.

Status : When a feature is approved in gerrit, the status field should be set
to closed.

Showing results of 70

# Summary▾ Milestone▾ Status▾ Owner▾ Created▾ Updated▾ Priority▾
113 examine ECDHE in tomcat - open 2013-09-26 2013-09-26 5  
112 components needs role field - open Ted Leung 2013-09-26 2013-09-26 5  
111 allow components to check if user has component enabled - open 2013-09-25 2013-09-25 5  
110 time zone localisation for patients viewing myoscar client/gui - open 2013-08-29 2013-08-29 5  
109 change survey templates to allow duplicate names if not active - open 2013-08-06 2013-08-06 5  
107 distributed event notification framework - internal and external - open 2013-07-12 2013-07-12 5  
106 ability for help_desk / support to view a persons preferences and maybe alter them - open 2013-07-08 2013-07-08 5  
105 proper patient data encryption & appointment of emergency access authority - pending Ted Leung 2013-06-14 2013-10-03 5  
104 myoscar_client first login should step you through a setup process. - open 2013-06-12 2013-06-12 5  
103 permissions v3, resimplification - open Ted Leung 2013-06-05 2013-06-05 5  
102 When in "sent" folder column "From:" should be changed to "To:" - accepted Hassan Abolhasssani 2013-05-09 2013-05-23 2  
101 missing asterisk for mandatory date field on immunisations page - open 2013-03-26 2013-05-15 2  
99 myoscar_client inactivity timeout feature - open 2013-03-12 2013-03-12 5  
93 auto-expire provider accounts - open 2013-01-15 2013-01-15 5  
90 Username formatting - open 2013-01-03 2013-01-03 5  
87 Integrate Readings None open 2012-08-13 2012-11-07 5  
85 Secure message - full email capabilities None open 2012-07-25 2012-11-07 5  
81 secure notes with data None open 2012-07-20 2012-11-07 5  
79 group functionality not complete yet None open 2012-07-10 2012-11-07 5  
78 generate summary reports None open 2012-07-06 2012-11-07 5  
76 update app workflow to have add/remove notifications None open 2012-07-04 2012-11-07 5  
75 eScheduling Reporting None open 2012-07-04 2012-11-07 5  
72 MyOscar Client group reports take a long time None open 2012-06-25 2012-11-07 5  
70 allow help_desk to view / alter relationships None open 2012-06-25 2012-11-07 9  
69 Explain medication fields None open 2012-06-25 2012-11-07 1  
  • Ticket Number
  • Summary
  • Milestone
  • Status
  • Owner
  • Creator
  • Created
  • Updated
  • Labels
  • Priority
 
(applies to this page only)
1 2 3 > >> (Page 1 of 3)
MongoDB Logo MongoDB