Issue #14852 open
Vlad Savitsky
created an issue

https://bitbucket.org/site/master/issues/4588/customisable-workflow

Marcus there is a pattern that is happening over and over. People want another state in the workflow that indicates the code needs to be tested: https://bitbucket.org/site/master/issue/5179/add-a-status-of-closed-to-issues I think most people just need one more state in the workflow. I mean really the "invalid" and "wontfix" state are superfluous. If you could kill one of those and replace it with "testing" or something I would and I'm sure many others would be happy. No need for custom workflows or complicated the notification just replace or add a state in the workflow.

Comments (14)

  1. Alastair Wilkes staff

    Duplicate of #4588. We really appreciate the feedback, but at this time we still do not plan to implement this. We are focused on improving code review/pull requests, CI/CD (pipelines), and backend changes to maintain high availability and improve performance.

  2. Vlad Savitsky reporter

    Issue #4588 closed with status 'wont fix' so this issue is not a duplicate but new one.

    I don't need "improving code review/pull requests, CI/CD (pipelines), and backend changes" but workflow is ugly.

  3. Alastair Wilkes staff

    Hi Vlad,

    I appreciate your persistence, but at the end of the day, issue #4588 is the master issue for this request. Opening additional issues dilutes votes on the master issue and makes it difficult to track the discussion around the request. If we decide to do this, we will reopen that request. Cool?

    Thanks,
    Alastair

  4. Vlad Savitsky reporter

    Hi Alastair,

    I was suprised that I still have a working account! Thanks for your patience.

    1. Issue #4588 closed and I can't reopen it because I'm not a reporter.
    2. As master issue closed I don't belive you ever implement it.
    3. Setting 'duplicate' status to this issue makes it also closed and you won't reopen it because it's not master issue.
    4. Seems you also suffer poor workflow statuses. Don't you?
  5. Log in to comment