Uploaded image for project: 'Crucible'
  1. Crucible
  2. CRUC-209

Repository mapping should force default if one-to-one match found

    • 1
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      Currently if a project is Crucible is set to have a default repository mapped, it still asks the user to specify which project they wish to create the review under. This is to accommodate the scenario in which multiple projects are mapped to the same repository.

      If there is only one Crucible project mapped to a given repository, when creating a review out of that repository, rather than asking the user to confirm the project, it should force the default mapping.

      The user could then override this in the review properties when assigning reviewers/moderators if required. Although being able to prevent this would be good too, probably as a project/repository mapping option "Allow users to chose another project instead of this default".

            [CRUC-209] Repository mapping should force default if one-to-one match found

            sladey added a comment -

            Feel free to reopen if you think the issue has not been addressed adequately in 2.0

            sladey added a comment - Feel free to reopen if you think the issue has not been addressed adequately in 2.0

            Why does the project need to be selected in advance at all?

            It can be amended when editing details, so why select it in advance? It seems to go against the "one click" creation style we are shooting for.

            Peter Moore [Atlassian] added a comment - Why does the project need to be selected in advance at all? It can be amended when editing details, so why select it in advance? It seems to go against the "one click" creation style we are shooting for.

            Yes, when creating a review (from changesets) and there is only one Project that is associated with the repository of those changesets, then that project should be assumed.

            Matt Quail (Inactive) added a comment - Yes, when creating a review (from changesets) and there is only one Project that is associated with the repository of those changesets, then that project should be assumed.

              Unassigned Unassigned
              a0568509078b Michael Shimmins
              Votes:
              1 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: