Uploaded image for project: 'Bamboo Data Center'
  1. Bamboo Data Center
  2. BAM-20003

Unclear plan state whilst cloning it

XMLWordPrintable

      Summary

      Previously to BAM-19856 there was a checkbox where users could choose if cloned plan would be enabled or disabled on creation whereas in most recent Bamboo versions (e.g 6.5.1, 6.6.0) buttons Clone or Save and continue are less clear to what plan state will be in comparison to older Bamboo version.

      Current behavior

      • Clone will create the plan in an enabled state
      • Save and continue will create the plan in a disabled state

            [BAM-20003] Unclear plan state whilst cloning it

            Martyna Wojtas (Inactive) made changes -
            Resolution New: Timed out [ 10 ]
            Status Original: Gathering Impact [ 12072 ] New: Closed [ 6 ]

            Martyna Wojtas (Inactive) added a comment -
            Atlassian Update - 23 June 2020

            Hi,

            Thank you for raising this issue. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request.

            This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers).

            Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.

            We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users.

            Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.

            Thank you,

            Bamboo Team

            Martyna Wojtas (Inactive) added a comment - Atlassian Update - 23 June 2020 Hi, Thank you for raising this issue. We regret to inform you that due to limited demand, we have no plans to implement it in the foreseeable future. In order to set expectations, we're closing this request. This is an automated update triggered by low user engagement with this suggestion (number of votes, number of watchers). Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Bamboo team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details. We understand how disappointing this decision may be but we want to be fully transparent when communicating with our users. Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments. Thank you, Bamboo Team
            Martyna Wojtas (Inactive) made changes -
            Labels Original: pse-request New: bamboo-bugs-grooming pse-request
            Pawel Skierczynski made changes -
            Status Original: Needs Triage [ 10030 ] New: Gathering Impact [ 12072 ]
            Monique Khairuliana (Inactive) made changes -
            Workflow Original: Bamboo Workflow 2016 v1 - Restricted [ 2747748 ] New: JAC Bug Workflow v3 [ 3384798 ]
            Status Original: Open [ 1 ] New: Needs Triage [ 10030 ]
            Owen made changes -
            Symptom Severity Original: Minor [ 14432 ] New: Severity 3 - Minor [ 15832 ]
            SET Analytics Bot made changes -
            Support reference count New: 1

            Deleted Account (Inactive) added a comment -

            Rafael, thanks for opening this request at my behest. I'd like to clarify the problem: With the new UI, nobody would realize that the sole difference between Clone and Save and Continue buttons is whether the new plan is enabled or disabled.

            Either the wording on the new button should be altered to describe it better, or perhaps the very obvious checkbox and its text should be brought back.

            Related to this issue is that, at least prior to the bug fix BAM-19856, the new cloned plan is enabled even if the original plan is disabled. So that means it isn't really being cloned. This new button verbiage makes that situation even less predictable by us common folk.

            Deleted Account (Inactive) added a comment - Rafael, thanks for opening this request at my behest. I'd like to clarify the problem: With the new UI, nobody would realize that the sole difference between Clone  and Save and Continue  buttons is whether the new plan is enabled or disabled. Either the wording on the new button should be altered to describe it better, or perhaps the very obvious checkbox and its text should be brought back. Related to this issue is that, at least prior to the bug fix BAM-19856 , the new cloned plan is enabled even if the original plan is disabled. So that means it isn't really being cloned. This new button verbiage makes that situation even less predictable by us common folk.
            Pawel Skierczynski made changes -
            Occurrence Factor New: 10% [ 12830 ]
            Symptom Severity Original: Major [ 14431 ] New: Minor [ 14432 ]
            Status Original: Needs Triage [ 10030 ] New: Open [ 1 ]
            Rafael Sperafico (Inactive) made changes -
            Labels New: pse-request

              Unassigned Unassigned
              rsperafico Rafael Sperafico (Inactive)
              Affected customers:
              1 This affects my team
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: