Feature changed by: Thomas Schmidt (digitaltomm) Feature #307613, revision 3 Title: Add Action Code Fields and Generate Email Texts According to Action Code Field openFATE: Unconfirmed Priority Requester: Important Requested by: Scott Couston (zczc2311) Description: Currently we open a new Feature request and the creator is not aware of any other action taken or added to the feature request. If a Feature is Closed due Dupe or invalid the creator is never aware of this. Other changes to the feature become lost to the original author. No one who contributes to the feature request ever gets an auto generated message as in current Bugzilla notifications. If the feature request is closed the author has no idea this has occured. -   Can we create an Action Code Field in each modification entry of any feature request. -   Here we can have default actions such as 'NEW' when a feature is created and the authors email added in the same manner as Bugzilla. -   Each additional comment can have a default Action code of 'ADDED-INFO' and add the authors email to this new entry. -   Each addition that clarifies or redefined the feature can have a 'CLARIFIED' or REDEFINED' action code field. -   The generation of messages of anything added to the feature request is subordinate and equal to the level of added entries and action code dependant. For example. The author of the creation of a feature will recieve email notification of ever addition to the feature. -   Anyone who add a third addition to the feature receives an email message and all subordinate entries back as far as the original author. -   Action code fields can be via Drop down menu box and the logic of selection of action code must be enforced. For example the First creation of a feature adds a mandatory NEW action code. This action would be the only non greyed out selection from the drop down list. -   The next entry, if the entry is to suggest 'REDEFINED' by drop down selection, would have 'NEW' greyed out and not accessible and leave 'REDEFINED' or 'CLARIFIED' or 'NEGATED'....etc available from drop down list. -   Once a new entry has been added to a feature request the previous entry action code field is not accessible. -   If the feature request gets 'ADDED-FUNCTION' and thereby put into production, no further entry's should be permitted and the feature locked with the exception of an added entry with the action code of 'COMMENT' from the drop down. Again message generation is equal and subordinate to the entry being added. -   For each and every Branch of comment or test-case a default action code filed should be maintained. -   Comments Please and I will manually check on this feature request's disposition. -   Scott -   -   + Discussion: + #1: Thomas Schmidt (digitaltomm) (2009-09-07 12:24:39) + openFATE uses hermes (https://hermes.opensuse.org/) for notifications. + You will get notifications about feature changes by selecting the + "feature changed" box. -- openSUSE Feature: https://features.opensuse.org/307613

Feature changed by: Thomas Schmidt (digitaltomm) Feature #307613, revision 5 Title: Add Action Code Fields and Generate Email Texts According to Action Code Field - openFATE: Unconfirmed + openFATE: Done Priority Requester: Important Requested by: Scott Couston (zczc2311) Description: Currently we open a new Feature request and the creator is not aware of any other action taken or added to the feature request. If a Feature is Closed due Dupe or invalid the creator is never aware of this. Other changes to the feature become lost to the original author. No one who contributes to the feature request ever gets an auto generated message as in current Bugzilla notifications. If the feature request is closed the author has no idea this has occured. Can we create an Action Code Field in each modification entry of any feature request. Here we can have default actions such as 'NEW' when a feature is created and the authors email added in the same manner as Bugzilla. Each additional comment can have a default Action code of 'ADDED-INFO' and add the authors email to this new entry. Each addition that clarifies or redefined the feature can have a 'CLARIFIED' or REDEFINED' action code field. The generation of messages of anything added to the feature request is subordinate and equal to the level of added entries and action code dependant. For example. The author of the creation of a feature will recieve email notification of ever addition to the feature. Anyone who add a third addition to the feature receives an email message and all subordinate entries back as far as the original author. Action code fields can be via Drop down menu box and the logic of selection of action code must be enforced. For example the First creation of a feature adds a mandatory NEW action code. This action would be the only non greyed out selection from the drop down list. The next entry, if the entry is to suggest 'REDEFINED' by drop down selection, would have 'NEW' greyed out and not accessible and leave 'REDEFINED' or 'CLARIFIED' or 'NEGATED'....etc available from drop down list. Once a new entry has been added to a feature request the previous entry action code field is not accessible. If the feature request gets 'ADDED-FUNCTION' and thereby put into production, no further entry's should be permitted and the feature locked with the exception of an added entry with the action code of 'COMMENT' from the drop down. Again message generation is equal and subordinate to the entry being added. For each and every Branch of comment or test-case a default action code filed should be maintained. Comments Please and I will manually check on this feature request's disposition. Scott Discussion: #1: Thomas Schmidt (digitaltomm) (2009-09-07 12:24:39) openFATE uses hermes (https://hermes.opensuse.org/) for notifications. You will get notifications about feature changes by selecting the "feature changed" box. #2: Thomas Schmidt (digitaltomm) (2009-10-26 00:11:06) As far as I understand, hermes provides the requested feature. To make this connection more visible, we should add a pointer on the feature page to show the notification system. + #3: Thomas Schmidt (digitaltomm) (2009-11-23 16:06:50) + The features now also have a direct link to hermes in the right + column. -- openSUSE Feature: https://features.opensuse.org/307613

Feature changed by: Thomas Schmidt (digitaltomm) Feature #307613, revision 7 Title: Add Action Code Fields and Generate Email Texts According to Action Code Field openFATE: Done Priority Requester: Important Requested by: Scott Couston (zczc2311) Description: Currently we open a new Feature request and the creator is not aware of any other action taken or added to the feature request. If a Feature is Closed due Dupe or invalid the creator is never aware of this. Other changes to the feature become lost to the original author. No one who contributes to the feature request ever gets an auto generated message as in current Bugzilla notifications. If the feature request is closed the author has no idea this has occured. Can we create an Action Code Field in each modification entry of any feature request. Here we can have default actions such as 'NEW' when a feature is created and the authors email added in the same manner as Bugzilla. Each additional comment can have a default Action code of 'ADDED-INFO' and add the authors email to this new entry. Each addition that clarifies or redefined the feature can have a 'CLARIFIED' or REDEFINED' action code field. The generation of messages of anything added to the feature request is subordinate and equal to the level of added entries and action code dependant. For example. The author of the creation of a feature will recieve email notification of ever addition to the feature. Anyone who add a third addition to the feature receives an email message and all subordinate entries back as far as the original author. Action code fields can be via Drop down menu box and the logic of selection of action code must be enforced. For example the First creation of a feature adds a mandatory NEW action code. This action would be the only non greyed out selection from the drop down list. The next entry, if the entry is to suggest 'REDEFINED' by drop down selection, would have 'NEW' greyed out and not accessible and leave 'REDEFINED' or 'CLARIFIED' or 'NEGATED'....etc available from drop down list. Once a new entry has been added to a feature request the previous entry action code field is not accessible. If the feature request gets 'ADDED-FUNCTION' and thereby put into production, no further entry's should be permitted and the feature locked with the exception of an added entry with the action code of 'COMMENT' from the drop down. Again message generation is equal and subordinate to the entry being added. For each and every Branch of comment or test-case a default action code filed should be maintained. Comments Please and I will manually check on this feature request's disposition. Scott Discussion: #1: Thomas Schmidt (digitaltomm) (2009-09-07 12:24:39) openFATE uses hermes (https://hermes.opensuse.org/) for notifications. You will get notifications about feature changes by selecting the "feature changed" box. #2: Thomas Schmidt (digitaltomm) (2009-10-26 00:11:06) As far as I understand, hermes provides the requested feature. To make this connection more visible, we should add a pointer on the feature page to show the notification system. #3: Thomas Schmidt (digitaltomm) (2009-11-23 16:06:50) The features now also have a direct link to hermes in the right column. #4: Roberto Mannai (robermann79) (2009-11-23 17:08:40) So when opening a new openFATE request, is not anymore mandatory to add oneself in the "Interested Persons" field? + #5: Thomas Schmidt (digitaltomm) (2009-11-23 18:03:17) (reply to #4) + No, it isn't. When you open a new request, your name is automatically + set as 'requester', and you will get notified if you subscribed to the + feature changes in hermes. -- openSUSE Feature: https://features.opensuse.org/307613