Create new item type from existing item type

GrantMore

Hi Mike,

Some thoughts:

Managing one Jama instance (as well as a sandbox instance and a staging instance) is a lot of work, never mind seven (plus the other instances of these servers - 21?)!

I understand your needs though. I can't help but imagine that the seven servers is one solution to the requirements, but one which is going to give you a lot of drawbacks and administrative overhead, particularly with synchronising the configuration as well as the data (and traceability?).

I've successfully persuaded people in the past that the Jama security is good enough for "top secret" projects to exist on the same instance. My experience is that it is. The whole concept of users not even seeing the project is usually a clincher in my experience.

In terms of active items, I'm in the processes of deploying Jama to a 15k head organisation at the moment, but it's early days so we only have a few 10k's of items. In a previous life, I had a Jama instance with 2.5k users and probably somewhere between 500k and 1M items. Zero performance issues to report. Ran beautifully worldwide on some pretty shady connections.

There was an issue which cropped up when the Stream function was launched due to the depth of hierarchy in our dataset, but that was quickly fixed by the Jama team.

I've been mulling the problem of the latent dataset building over time and potentially degrading server performance for a while. I've not seen this issue to date, but being future-proof is important. 20M items is easily achievable and I understand how you got there.

I think the distinction between "Active" and "Archived" projects to minimise true WIP and allow dormant data to be archived is a good concept.

For example, when a project has had no activity for two years, it can be archived. The tool can then treat it as a dormant project which is put to one side (i.e. not in active project lists). The performance is then based on active projects rather than the active plus archived projects. A rolling window, if you will.

Active projects are open for use by all users. Archived projects are only visible to administrators and are stored on the basis that they're recoverable, but not in active WIP (i.e. visible to all users).

I can see that this forces users to manage IP libraries as WIP or lose the IP, but the performance improvement is the key benefit.

I've no idea if this is how archiving ACTUALLY works on Jama...

In terms of external customers, I only ever give them review centre licenses and collaborate via the ready-firewalled review centre. That's worked really well for me to date. What's the information you need to share?

Cheers,
Grant

GrantMore

Spot on.

Victor Cheung

Adding my vote for this feature!