IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'HipChat'
  1. HipChat
  2. HCPUB-3253

Automatically room ownership fallback sorting

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    • Icon: Suggestion Suggestion
    • Resolution: Won't Fix
    • None
    • Room administration
    • 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.

      Hi Atlassian,

      I have a question / feature request regarding HipChat Rooms.

      As is:

      Everytime an owner of a room leaves the company or the account is deactivated due to other reasons the room ownership of rooms owned by one of the mentioned colleagues goes over to me (admin). The result is a long list of rooms (private and public) that are owned by me as "Room Admin" (https://yourserver.domain/admin/rooms?t=mine). The listed rooms are sorted alphabetically and there is no chance to change the order (i.e. "Last Active" or "Messages Sent") what could be some kind of indicator to archive or delete them or better switch the ownership to a responsible colleague.

      Question:

      Is there a way planned (or already implemented and I haven`t found it) to "clean up " these rooms in a comfortable way? Would be nice to have a similar script like the "trailing_monthly_user_activity.sh" script or some kind of filter in the GUI.

      Additionally some kind of bulk change for room ownerships would be nice.

      Thanks a lot,
      Carlo

        1. 1Z0-820-Exam-Dumps-2018.pdf
          216 kB
          andreshacklefo.rd88

          Form Name

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'HipChat'
            1. HipChat
            2. HCPUB-3253

            Automatically room ownership fallback sorting

            This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

              • Icon: Suggestion Suggestion
              • Resolution: Won't Fix
              • None
              • Room administration
              • 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.

                Hi Atlassian,

                I have a question / feature request regarding HipChat Rooms.

                As is:

                Everytime an owner of a room leaves the company or the account is deactivated due to other reasons the room ownership of rooms owned by one of the mentioned colleagues goes over to me (admin). The result is a long list of rooms (private and public) that are owned by me as "Room Admin" (https://yourserver.domain/admin/rooms?t=mine). The listed rooms are sorted alphabetically and there is no chance to change the order (i.e. "Last Active" or "Messages Sent") what could be some kind of indicator to archive or delete them or better switch the ownership to a responsible colleague.

                Question:

                Is there a way planned (or already implemented and I haven`t found it) to "clean up " these rooms in a comfortable way? Would be nice to have a similar script like the "trailing_monthly_user_activity.sh" script or some kind of filter in the GUI.

                Additionally some kind of bulk change for room ownerships would be nice.

                Thanks a lot,
                Carlo

                  1. 1Z0-820-Exam-Dumps-2018.pdf
                    216 kB
                    andreshacklefo.rd88

                        Unassigned Unassigned
                        54f9b8d67173 Carlo Hohenbrink
                        Archiver:
                        mandreacchio Michael Andreacchio

                          Created:
                          Updated:
                          Resolved:
                          Archived:

                            Unassigned Unassigned
                            54f9b8d67173 Carlo Hohenbrink
                            Archiver:
                            mandreacchio Michael Andreacchio

                              Created:
                              Updated:
                              Resolved:
                              Archived: