Uploaded image for project: 'FishEye'
  1. FishEye
  2. FE-699

Allow Perforce respository definition via a client spec

    • Icon: Suggestion Suggestion
    • Resolution: Duplicate
    • None
    • Indexing
    • 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.

      I would like finer control over what Fisheye puts into repository. In Perforce terms, this is usually done via a client specification (instead of just a simple path). For instance, I have a repository path that has numerous sub directories, however, a few of the sub directories have different security requirements. I would like do define a single Fisheye repository that selects all the sub-directories that are unrestricted and another one for the security restricted sub directories

            [FE-699] Allow Perforce respository definition via a client spec

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3022658 ] New: JAC Suggestion Workflow 3 [ 3642315 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Marek Parfianowicz made changes -
            Component/s New: Indexing [ 41890 ]
            Component/s Original: vcs-Perforce [ 12291 ]
            Labels New: p4 perforce
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2949211 ] New: JAC Suggestion Workflow [ 3022658 ]
            Owen made changes -
            Workflow Original: FECRU Development Workflow - Triage [ 943742 ] New: Confluence Workflow - Public Facing v4 [ 2949211 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Owen made changes -
            Backlog Order (Obsolete) Original: 9420000000
            Issue Type Original: Improvement [ 4 ] New: Suggestion [ 10000 ]
            Piotr Swiecicki made changes -
            Workflow Original: FECRU Development Workflow (Triage) [ 309186 ] New: FECRU Development Workflow - Triage [ 943742 ]
            Seb Ruiz (Inactive) made changes -
            Workflow Original: Simple review flow with triage [ 155903 ] New: FECRU Development Workflow (Triage) [ 309186 ]
            sladey made changes -
            Resolution New: Duplicate [ 3 ]
            Status Original: Needs Triage [ 10030 ] New: Closed [ 6 ]
            BrendanA made changes -
            Status Original: Open [ 1 ] New: Needs Triage [ 10030 ]
            BrendanA made changes -
            Workflow Original: Copy of review flow with triage [ 154170 ] New: Simple review flow with triage [ 155903 ]

              cmacneill Conor (Inactive)
              bob.swift Bob Swift
              Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

                Created:
                Updated:
                Resolved: