You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "SebastianWagner (JIRA)" <ji...@apache.org> on 2012/10/25 14:05:11 UTC
[jira] [Created] (OPENMEETINGS-453) Recordings associated with
wrong user after import if already a user was in the database
SebastianWagner created OPENMEETINGS-453:
--------------------------------------------
Summary: Recordings associated with wrong user after import if already a user was in the database
Key: OPENMEETINGS-453
URL: https://issues.apache.org/jira/browse/OPENMEETINGS-453
Project: Openmeetings
Issue Type: Bug
Reporter: SebastianWagner
Seems like the userId switch is not implemented when importing recordings.
So they are associated with the wrong user id, in case there was already a user in the database when importing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (OPENMEETINGS-453) Recordings associated with
wrong user after import if already a user was in the database
Posted by "Maxim Solodovnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik resolved OPENMEETINGS-453.
-------------------------------------------
Resolution: Fixed
Fix Version/s: 2.1 Apache Incubator Release
> Recordings associated with wrong user after import if already a user was in the database
> ----------------------------------------------------------------------------------------
>
> Key: OPENMEETINGS-453
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-453
> Project: Openmeetings
> Issue Type: Bug
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
> Fix For: 2.1 Apache Incubator Release
>
>
> Seems like the userId switch is not implemented when importing recordings.
> So they are associated with the wrong user id, in case there was already a user in the database when importing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (OPENMEETINGS-453) Recordings associated with
wrong user after import if already a user was in the database
Posted by "Maxim Solodovnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OPENMEETINGS-453?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Maxim Solodovnik reassigned OPENMEETINGS-453:
---------------------------------------------
Assignee: Maxim Solodovnik
> Recordings associated with wrong user after import if already a user was in the database
> ----------------------------------------------------------------------------------------
>
> Key: OPENMEETINGS-453
> URL: https://issues.apache.org/jira/browse/OPENMEETINGS-453
> Project: Openmeetings
> Issue Type: Bug
> Reporter: SebastianWagner
> Assignee: Maxim Solodovnik
>
> Seems like the userId switch is not implemented when importing recordings.
> So they are associated with the wrong user id, in case there was already a user in the database when importing.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira