The idea is, to mark the parent User Story as "In Progress" as soon as a related task leaves the initial status.
For our bug handling, we use a few states: more info, rejected, in progress, fixed, closed, etc. When a bug is finally closed, we have no way of looking into the history to find why it was closed; was it rejected initially, or was it a code fix. (I tried to create a custom report to figure this out but had no luck.)
For our bug handling, we use a few states: more info, rejected, in progress, fixed, closed, etc. When a bug is finally closed, we have no way of looking into the history to find why it was closed; was it rejected initially, or was it a code fix. (I tried to create a custom report to figure this out but had no luck.)
For our bug handling, we use a few states: more info, rejected, in progress, fixed, closed, etc. When a bug is finally closed, we have no way of looking into the history to find why it was closed; was it rejected initially, or was it a code fix. (I tried to create a custom report to figure this out but had no luck.)
For our bug handling, we use a few states: more info, rejected, in progress, fixed, closed, etc. When a bug is finally closed, we have no way of looking into the history to find why it was closed; was it rejected initially, or was it a code fix. (I tried to create a custom report to figure this out but had no luck.)
For our bug handling, we use a few states: more info, rejected, in progress, fixed, closed, etc. When a bug is finally closed, we have no way of looking into the history to find why it was closed; was it rejected initially, or was it a code fix. (I tried to create a custom report to figure this out but had no luck.)
For our bug handling, we use a few states: more info, rejected, in progress, fixed, closed, etc. When a bug is finally closed, we have no way of looking into the history to find why it was closed; was it rejected initially, or was it a code fix. (I tried to create a custom report to figure this out but had no luck.)
For our bug handling, we use a few states: more info, rejected, in progress, fixed, closed, etc. When a bug is finally closed, we have no way of looking into the history to find why it was closed; was it rejected initially, or was it a code fix. (I tried to create a custom report to figure this out but had no luck.)
For our bug handling, we use a few states: more info, rejected, in progress, fixed, closed, etc. When a bug is finally closed, we have no way of looking into the history to find why it was closed; was it rejected initially, or was it a code fix. (I tried to create a custom report to figure this out but had no luck.)
For our bug handling, we use a few states: more info, rejected, in progress, fixed, closed, etc. When a bug is finally closed, we have no way of looking into the history to find why it was closed; was it rejected initially, or was it a code fix. (I tried to create a custom report to figure this out but had no luck.)
For our bug handling, we use a few states: more info, rejected, in progress, fixed, closed, etc. When a bug is finally closed, we have no way of looking into the history to find why it was closed; was it rejected initially, or was it a code fix. (I tried to create a custom report to figure this out but had no luck.)
For our bug handling, we use a few states: more info, rejected, in progress, fixed, closed, etc. When a bug is finally closed, we have no way of looking into the history to find why it was closed; was it rejected initially, or was it a code fix. (I tried to create a custom report to figure this out but had no luck.)
In v.3.5.3. we've released about 20 predefined rules that you can enable.
http://guide.targetprocess.com/settings/custom-rules.htmlLater we are going to provide a possibility to create your own custom rules. Please share your feedback!
For our bug handling, we use a few states: more info, rejected, in progress, fixed, closed, etc. When a bug is finally closed, we have no way of looking into the history to find why it was closed; was it rejected initially, or was it a code fix. (I tried to create a custom report to figure this out but had no luck.)
When changing defect state we can make comments mandatory which is useful. Expanding that idea, it would be useful if we also pick other fields (including custom fields) to be mandatory (so when closing we could give...
Allow customers to view Boards with Requests, add new Requests, vote for Requests, etc — without any additional license.
UX and Implementation started this week
TP2/3 is already very flexible and that's great!
However there is still a non-customizable fixed entity structure:
(besides bugs and test plans)
- Request
- Feature
- User Story
- Task
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.
By now we manage by...
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.
http://www.targetprocess.com/agileproductblog/2014/09/upcoming-feature-epics-as-one-more-hierarchy-level.html
Accepted, but not in the next 6 months for sure