Uploaded image for project: 'AppFormer'
  1. AppFormer
  2. AF-2891

Space's default archetype is not respected when creating a new project

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • None
    • None
    • AppFormer Foundation

    Description

      1.Proposed title of this feature request
      [GSS-RFE] Space's default archetype is not respected when creating a new project

      2. Who is the customer behind the request?
      Account: BBVA/#5841948
      TAM customer: Yes
      SRM customer: No
      Strategic: Yes
      Tactical: No

      3. What is the nature and description of the request?
      **
      Currently, you can set a default archetype for new projects in a given space (post with more details), but you still need to click on advanced options and based on a template.
      The requirement is to be able to create on BC all new projects based on a default template without having to go on advanced options, and select "Based from template"
       
      4. Why does the customer need this? (List the business requirements here)**

      Create on BC all new projects based on a default template without having to go on advanced options, and select "Based from template"

      5. How would the customer like to achieve this? (List the functional requirements here)

      They want to have the ability to create new project based on "Default" archetype without having to go on advanced options, and select "Based from template"

      6. For each functional requirement listed, specify how Red Hat and the customer can test to confirm the requirement is successfully implemented.

      1. Add the archetype in business administration console
      2. The status of this archetype should be "Default"
      3. In Space setting select it as "Default"
      4. Create a new project of "Default" template marked before in Space/Business view, without selecting the "Based on Template" checkbox

      7. Is there already an existing RFE upstream or in Red Hat Bugzilla?

      No

      8. Does the customer have any specific timeline dependencies and which release would they like to target?

      No

      9. Is the sales team involved in this request and do they have any additional input?

      No

      10. List any affected packages or components.

      No

      11. Would the customer be able to assist in testing this functionality if implemented?

      Yes.

      Attachments

        Activity

          People

            abkuma abhishek kumar
            abkuma abhishek kumar
            Barbora Siskova Barbora Siskova
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: