Jive Software Open Source

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What’s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Spark
  • SPARK-102

Changing temp conf room name to permanent name leads to odd behavior

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Cannot Reproduce
  • Affects Version/s: 1.1.0
  • Fix Version/s: 2.6.0
  • Component/s: None
  • Labels:
    None
  • Acceptance Test - Add?:
    Yes
  • Acceptance Test - Entry:
    Hide

    See description.

    Show
    See description.

Description

There is some odd behavior in the following scenario:
[1] User qa1 chatting with user marilyn.
[2] User qa1 clicks on Conference button in chat window.
[3] In the conference poput, change the room name from qaNNN to just qa, which is the name of an existing permanent room.
Pop up disappears, but no conference tab is displayed.
[4] Repeat steps 2 and 3.
Same behavior.
[5] Back in qa1's main window, click on conference tab and select qa conference room.
Now, in the chat window, there suddenly 3 tabs for conference room "qa".

So apparently the display of tabs for the qa conf room got queued up from the earlier steps, but they were only displayed when entered through the main conference UI.

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
Marilyn Daum added a comment - 12/02/05 01:58 AM

Further behavior from scenario after step 5:
[6] User qa1 posts text to the chat room in each of the 3 tabs.
In one of the other tabs for that room, the post appears as coming from user "null".

We need to tighten up attempts to join the same conf room from different paths.

Show
Marilyn Daum added a comment - 12/02/05 01:58 AM Further behavior from scenario after step 5: [6] User qa1 posts text to the chat room in each of the 3 tabs. In one of the other tabs for that room, the post appears as coming from user "null". We need to tighten up attempts to join the same conf room from different paths.
Hide
Permalink
wroot added a comment - 11/11/09 08:23 PM

Can't reproduce this with the latest SVN version. Popup is not shown upon ad-hoc group chat creation. If user goes to room configuration, he can change room's name to whatever he wants. Only the name will be changed, not the Room's ID. So there is no interference and users can still chat in that ad-hoc room and are not affecting other permanent room with the same name.

Show
wroot added a comment - 11/11/09 08:23 PM Can't reproduce this with the latest SVN version. Popup is not shown upon ad-hoc group chat creation. If user goes to room configuration, he can change room's name to whatever he wants. Only the name will be changed, not the Room's ID. So there is no interference and users can still chat in that ad-hoc room and are not affecting other permanent room with the same name.

People

  • Assignee:
    Andrew Seymour
    Reporter:
    Marilyn Daum
Vote (1)
Watch (1)

Dates

  • Created:
    12/02/05 01:51 AM
    Updated:
    11/11/09 08:23 PM
    Resolved:
    11/11/09 08:23 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for igniterealtime.org. Try JIRA - bug tracking software for your team.