Michael Dubakov
536
Started 3 days ago

Automatic Rules (various) / Custom Business Rules

Having status like "In Progress" cascade up (not down) would be extremely useful, quite often we find that a task is marked as in progress but the developer does not update the user story or feature so its quite hard to track progress from an overview.

Cascading this up so Task -> User Story -> Epic but not down so marking a user story as in progress does not impact tasks etc would massively improve this. Also linking to requests in some way may be nice but that is less clear cut on how the flow will work, any related item marked in progress then request is in progress?

Even if there is the possibility to change the name of the entities and add custom fields, in some cases it may be necessary to insert new kind of entities within the structure. This is the case of our company in which we need (to complain with ISO standards) to also manage audits, user requirements, system requierements and more independent and hierarchically dependent entities.

  • pdf
    Automatic Rules
    23Mb
  • zip
    Rule-engine-inkspace
    65Kb
  • Preview
    Screenshot 2015 02 06 at 12.38.39 PM
Sergio Anza February 9, 2015
Latest official comment
Michael Dubakov Targetprocess October 10, 2014

Most likely we postpone custom hierarchy for next year, but we are adding some flexibility into Targetprocess.

Firs thing is Epic entity above Feature entity. If you need this functionality, please check the solution and provide a feedback, it would be really helpful! Epics implementation is started actually.

Show 23 replies
351 comments Show newest first
  • Anonymous October 10, 2014

    If i create a US from a request. Is it possible to automatically close the request when US it is Done?

    Hide comments
  • Michael Dubakov Targetprocess October 10, 2014

    We would like to set a custom field when a user story/bug is added to a team iteration after it has started.

    Show 23 replies
  • Natalie Yadrentseva Targetprocess October 9, 2014

    One more vote for the ability to notify users from related entities when an entity is done. Otherwise we have to manually close and notify all requests which are connected to a story when it is closed.

  • Florian Schmitz October 3, 2014

    I would like to prevent tasks from being created without team. So I'd suggest the possibility of defining a default project for each team (we have at least two projects per team, so the currently existing rule for user stories does not help) + a custom rule to automatically set the default project if no team is set (for all task types).

    • Anonymous October 10, 2014

      If i create a US from a request. Is it possible to automatically close the request when US it is Done?

      • Anonymous October 10, 2014

        I would also like a rule that assigns a task automatically to a QS engineer when it moves to a certain state.

      • Florian Schmitz October 3, 2014

        When we change a US from state to state, a certain FILE or Attached Google Drive Document (you already have a mashup for that), could be automatically added to that US.

        As far as I can tell, that would be a killing feature. :)

        Keep up the great work btw!

  • Anonymous October 3, 2014

    If i create a US from a request. Is it possible to automatically close the request when US it is Done?

One comment was not deleted because of problems with server