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

Allow inactive FishEye users

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 4.0.0
    • None
    • None

    • 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.

      You have to delete users from FishEye to stop them logging in and taking up a user license. However that means you lose author mappings for the deleted user.

      We should allow users to create author mappings for users that do not exist in FishEye so they can mark the users inactive, but still maintain some sort of logical display name in FishEye.

            [FE-2709] Allow inactive FishEye users

            Lukasz Pater added a comment -

            As of FishEye/Crucible 4.0.0 you can define which user groups have permission to use FishEye (and consume a license), using the new global permissions screen. Users without the permission don't consume the license, and can't log in or use the application, but don't need to be deleted.

            Lukasz Pater added a comment - As of FishEye/Crucible 4.0.0 you can define which user groups have permission to use FishEye (and consume a license), using the new global permissions screen. Users without the permission don't consume the license, and can't log in or use the application, but don't need to be deleted.

            Kevin Ober added a comment -

            This is most bothersome for me in Crucible reviews. They display who last changed the lines of code you're looking at, which is nice, but non-existent users are displayed as "LastName, FirstName <emailaddress@emailprovider.com>", which takes up a lot of the screen real estate on the review. Independent of the true fix of setting up author mappings for inactive users, can Crucible be changed to simply strip off the email address in the history display? Should I submit a separate Crucible issue for that?

            Kevin Ober added a comment - This is most bothersome for me in Crucible reviews. They display who last changed the lines of code you're looking at, which is nice, but non-existent users are displayed as "LastName, FirstName <emailaddress@emailprovider.com>", which takes up a lot of the screen real estate on the review. Independent of the true fix of setting up author mappings for inactive users, can Crucible be changed to simply strip off the email address in the history display? Should I submit a separate Crucible issue for that?

            Michael Virnstein added a comment -

            this is especially true, if you use JIRA as authentication service. I think users should be counted against the fisheye license, if they have the right to access fisheye.
            Currently you always have the right to log into fisheye, when you are in the list of users. I think this should be changed to a system like it is used in JIRA.

            Michael Virnstein added a comment - this is especially true, if you use JIRA as authentication service. I think users should be counted against the fisheye license, if they have the right to access fisheye. Currently you always have the right to log into fisheye, when you are in the list of users. I think this should be changed to a system like it is used in JIRA.

              Unassigned Unassigned
              andrew.myers Andrew Myers [Atlassian]
              Votes:
              13 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: