You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 10 Next »

Scope

  • New Features might be developed and included in next Releases - these Features need to be planned
  • This article describes our policy for handling this situation and its mapping with the states in JIRA.

Life Cycle

Planned features will pass through the following states:

OPEN

  • A feature has been described and assigned
  • The next step will be to decide, whether the feature is a Known Issue or it has to be Clarified.

KNOWN ISSUE

  • This is not a feature, it is a known issue and will by purpose not be changed.
  • Known Issue is an end status, there is no further decision taken.

CLARIFY

  • The feature has to be first discussed before a further state is decided
  • The feature can be then dismissed or accepted.

DISMISSED or ACCEPTED

  • In case the feature is NOT going to be implemented, it will be set to Dismissed.
    • Dismissed is an end status, there is no further decision taken.
  • In case the feature is going to be implemented, it will be set to Accepted.
    • At that point, the Development of the feature can be initiated.

DEFERRED 

  • The feature is going to be developed because it has been Accepted
  • Even though, the feature is not going to be developed for the Planned Release.
  • Another future Release will be assigned to it in order for this feature to be developed.
  • No labels