• Votes

    1

    Baseline: Link only approved baselines to file release

    A File release represents the outcome of a development. As a unambiguous reference, the project manager links the approved baseline to the file release. To avoid ...
  • Votes

    3

    Set artifact fields by commit

    When commiting code changes, [artf1234] can be used to create an association between the commit and the artifact. Additional options should be available to set fields in ...
  • Votes

    1

    Upgrade Subversion version

    TeamForge v19.2 ships with Subversion v1.8.19 which is 2 years old.
  • Votes

    1

    Sum Effort should not round all values

    In our WoW the actual effort will be updated by state. Furthermore we have a separate field “Actual Effort (Per State)” that is mandatory to fill in order to switch to ...
  • Votes

    1

    Display annotation in tags view

    The web UI for SCM shows in the tab "tags" the list of tags with the according SHA-1 commit link. But it doesn't show the annotation which is a more detailed description ...
  • Votes

    1

    For baseline creation, use predefined SCM tags from baseline ...

    Use case: My project uses a specific version of a library which rarely or never changes between releases, e.g. firmware, os or standard components. When I create a ...
  • Votes

    3

    tracker/planning folder view: "show summary" always disappears

    In the tracker/planning folder view, when I select "show summary" the system shows the summary. But when I select or reselect any tracker/planning folder, the summary ...
  • Votes

    1

    Mass update "status" of documents

    Use case After a workshop/review session, a user needs to update the status of all discussed documents. Similar to tracker, the function "mass update" for the document ...
  • Votes

    4

    Association shall update "last Modified"

    Observation Adding an association to a tracker artifact doesn't change the "last Modified" timestamp. Issue Users are not aware of new associations, e.g by commits or ...
  • Votes

    3

    Search for text in brackets

    Use case My developers use some abbreviations in tracker title to define the component, subsystem or OEM, e.g. "[ME][AND]No signal received from ..." It shall be possible ...
  • Votes

    3

    In Plan view, when the system sums-up hours, it should also display ...

    The project is defined to use for all the artifacts effort calculations 'Hours'. However, in the 'Plan' view, the total hours is not displaying, instead the total point ...
  • Votes

    1

    Clone and associate document review

    Use case: When I launch a "document review" and get review findings, I need to be able to follow-up these findings until resolution. I create a tracker artifact for every ...
  • Votes

    1

    Document permissions: Document creator shall have the right to delete ...

    Use Case: A user creates a document in TF doc. Then he/she realizes that something was wrong and want to delete the document again. But the user has no right to delete ...
  • Votes

    1

    Association tab for commit: Add Git Repository Name

    In the association tab of artifacts, the link to a commit displays only the project name in the column source. It would be very beneficial to display the Git repository ...
  • Votes

    2

    Fetching Inherited Roles

    Currently only while looking at a Users profile and Roles within there we can see the roles he inherits from Parent projects. We create monthly reports using CLI for ...
  • Votes

    2

    hide fields in the tracker artifact

    It should be possible to hide fields in a Tracker definition. Some fields will require a default to be defined. Currently we also use Trackers for purposes that ...
  • Votes

    2

    Reparent of child artifact should be a one-step action.

    Changing the parent of a set of artifact is currently very painful. A lot of modifications have to be executed: - remove parent from child. - change planning ...
  • Votes

    3

    Tracker artifact attribute values must be read-only

    When we exchange Tracker artifacts with other lifecycle management tools, we want to have one system in the lead at any moment in time. Therefore when artifacts are ...
  • Votes

    2

    TeamForge releases should be complete

    Currently a TeamForge release is not always complete. The TeamForge application integrates with Subversion Edge, has training material which depends on the version, the ...
  • Votes

    1

    TeamForge should be always on

    When TeamForge is maintained or updated, the end-users should not suffer from this action. An upgrade should be instantaneous and therefore the application should be ...