Enable demotion/promotion to GL stages linked to off-normal states Hot

by Darren McLaughlin on July 02, 2015
Demotion/promotion of an object to a GL stage linked to off-normal state should behave the same as to a normal state.
  • If a GL stage is linked to a normal request lifecycle state, the object is promoted or demoted to that stage when the object is actioned to that state. However, this does not apply to off-normal states. GL stages linked to off-normal states should work the same way. While it might be understandable that an object could not be demoted/promoted if it is already IN and off-normal, an object should still be able to be demoted/promoted if it's actioned TO that state. The way the linkage of a GL stage to an off-normal state behaves is the same as if it's not linked at all. This should be up to the user to choose what the behavior would be by either linking a GL stage to that state or not.

    If an object is in a higher stage and it is set to an off-normal state, we'll often want that object to be demoted. The way it works now, it is necessary to remember to demote the object before actioning it. This defeats the purpose of linking GL stages to object lifecycle states.

    Ideas

    Status
  • Please login to view any attachments.

  • It's not really a matter of how likely it is to action to an off-normal state. If it's done only once after an object has been promoted, that's enough. When an object is actioned to an off-normal state, the GL stage is the same whether a GL stage is linked to a lifecycle state or not, so there is no reason to have it behave differently. It should be up to the user to decide what the off-normal state is used for and whether an object is demoted/promoted or not when it is actioned to that state. If the user wants the object to behave the way it does not, then it's just don't link a GL stage with that state. Also, it should be up to the user as to whether an object already in an off-normal state should be demoted/promoted or not. It's not unreasonable that an object that has been promoted to be actioned to an off-normal state. As the behavior is now, it can never be demoted unless it is first actioned (again) to a normal state, demoted, then actioned back to the off-normal state.

    We have multiple levels of a build. One might can promote an object to a 'test' build, the first level, then decide later that the object is no longer needed and perhaps even unwanted in the final production build and actioned to an off-normal state. Also, the off-normal state does not necessarily have to mean the object is unwanted. There may be other uses. At a minimum, assuming Serena wants to enforce the idea that 'off-normal' means obsolete/unwanted, one should still be able to automatically demote an object actioned to an off-normal state.
    Darren McLaughlin Commented by Darren McLaughlin July 07, 2015
    Top 100 Reviewer  -  

    It's not really a matter of how likely it is to action to an off-normal state. If it's done only once after an object has been promoted, that's enough. When an object is actioned to an off-normal state, the GL stage is the same whether a GL stage is linked to a lifecycle state or not, so there is no reason to have it behave differently. It should be up to the user to decide what the off-normal state is used for and whether an object is demoted/promoted or not when it is actioned to that state. If the user wants the object to behave the way it does not, then it's just don't link a GL stage with that state. Also, it should be up to the user as to whether an object already in an off-normal state should be demoted/promoted or not. It's not unreasonable that an object that has been promoted to be actioned to an off-normal state. As the behavior is now, it can never be demoted unless it is first actioned (again) to a normal state, demoted, then actioned back to the off-normal state.

    We have multiple levels of a build. One might can promote an object to a 'test' build, the first level, then decide later that the object is no longer needed and perhaps even unwanted in the final production build and actioned to an off-normal state. Also, the off-normal state does not necessarily have to mean the object is unwanted. There may be other uses. At a minimum, assuming Serena wants to enforce the idea that 'off-normal' means obsolete/unwanted, one should still be able to automatically demote an object actioned to an off-normal state.

    Hi Darren. Can you describe the lifecycle of your request, including normal and off normal states? Often a request would have less likelihood of hitting an off-normal state (such as rejected, on hold,..) once it has been promoted the first time - at least when using other requests to deal with things like testing defects.
    Garry Womack Commented by Garry Womack July 06, 2015
    Top 50 Reviewer  -  

    Hi Darren. Can you describe the lifecycle of your request, including normal and off normal states? Often a request would have less likelihood of hitting an off-normal state (such as rejected, on hold,..) once it has been promoted the first time - at least when using other requests to deal with things like testing defects.

     

PrintEmail

Recent Tweets