Re: Moving Cayenne Jira to a shared instance

[Andrus Adamchik <an...@objectstyle.org>]

Hi Jeff,

Thanks for clarification. I do understand the challenge in merging  
two dbs. Until yesterday I just wasn't sure if this problem has been  
already solved by the Jira team. BTW, I think we can simplify the  
task. What's important is loading the issues and merging users and  
groups (resolving potentially conflicting names). We have no custom  
fields and we can manually recreate permission and notification  
schemes. Does it make things simpler?

Also after our yesterday conversation I opened an improvement request  
regarding single sign-on part of this discussion:

http://jira.atlassian.com/browse/JRA-9930

Andrus


On Apr 19, 2006, at 5:03 PM, Jeff Turner wrote:

> On Mon, Apr 17, 2006 at 07:43:48PM +0400, Andrus Adamchik wrote:
>> Jeff,
>>
>> Before I open an INFRA issue on that, I wanted to check with you. Our
>> new Jira works well, but there is a strong sentiment among our
>> mentors and committers that we should be moved to a shared Apache
>> Jira instance.
>
> There is an equally strong sentiment amongst infra people, because one
> Jira is easier to maintain than 4 (and counting) and uses less memory.
> However, merging relational datasets is not the easiest thing to do.
> Conflicts potentially arise with users, permission schemes,  
> notification
> schemes, custom fields, field screens.. pretty much every admin-level
> object that relates to a project. Inter-project issue links may break,
> user dashboards refer to now nonexistent projects, etc.
>
> The relevant feature request for JIRA is:
>
> http://jira.atlassian.com/browse/JRA-1604
>
> A simpler approach is to allow single sign-on by reusing a single user
> database (userbase).  This would require some work on OSUser, the  
> library
> JIRA uses for user/profile management:
>
> http://opensymphony.com/osuser/
>
> Specifically, although OSUser allows two differently configured
> ProfileProviders, they would both reuse the same PropertySet instance
> (where user profile details are looked up). Some work needs to be  
> done so
> that each ProfileProvider can be configured with its own PropertySet.
> I've been playing around on my laptop, but can't promise anything.
>
> Hope that clarifies things :) Feel free to forward to people who  
> might be
> inclined to vote for the issue above.
>
>
> --Jeff