Feature Wiki

Information about planned and released features

Tabs

Show Points from Sub Trees

1 Requirements

In the current implementation of the study programme, the points of a subnode only get counted in a topnode if the user has the required amount of points in the subnode. That is, from the perspective of the topnode, the subnode switches its amount of points from 0 to the required amount of points as soon as a user gathered enough points. This also influences the progress bar the user sees on her personal desktop, as it might show 0 percent on the root node of a program for a long time when the programm is nested.

The user story for this requirement thus is:

A user gathered 60 out of 90 required points in a node, which is not the root node of the study programme. On his personal desktop the user first sees the root node of the programm, which already shows the 60 points and according percentage when the user did not complete a node below the root node.

To implement this requirement, the following considerations should be taken into account:

As the visible progress and the de facto progress should be in sync this requirement needs to be addressed by a setting influencing the counting of points on nodes. As the current idea of the study programme is, that every nodes reports points and success data to its parent, the setting should live at the sub node, not the topnode.

Therefore, to implement this requirement, a new setting 'Reporting of Points to Parent' on study programm nodes is needed, that has the two options 'Only Report Points when Required Points are Gathered" which represents the currently implemented behaviour, where a new option 'Report All Points Up To Required Points' represents the new behaviour.

In both modes every node will not report more points than the required points set on the node.

2 Additional Information

  • Idea / concept: Marko Glaubitz, Richard Klees <richard.klees@concepts-and-training.de>
  • Interest in funding: (please indicate if you are interested/able to fund this feature)
  • Maintainer: Richard Klees <richard.klees@concepts-and-training.de>
  • Implementation of the feature is done by (will be set by Jour Fixe / maintainer)
  • Testcases by: (please add your name if you want to create the testcases for this feature)

3 Discussion

4 Implementation

{please give a description of the final implementation and add screenshots if possible}

Test Cases

Test cases completed at {date} by {user}

  • {Test case number linked to Testrail} : {test case title}

Approval

Approved at {date} by {user}.

Last edited: 15. Mar 2016, 13:02, Klees, Richard [rklees]