Support

Expand all | Collapse all

To break or not to break the JAMA Sync after a Project is over?

  • 1.  To break or not to break the JAMA Sync after a Project is over?

    Posted 06-18-2018 11:22

    We have a main project where we keep the master list of requirements, test cases, defects etc. We also have multiple sub project which might have few new items as well as synced items from main project. When this new Project is over we sync the updates back to the main project.
    The question is whether to keep the sync or break it at that point? We will be running multiple projects at the same time and can multiple project items be in sync with the main project at same time.

    Could you point us to some best practices with Reuse and sync in multi project architecture? Are there performance implications if we have a large number of sync'ed items? Also can we restrict the permissions on sync?




    ------------------------------
    Sri

    Hill-Rom Clinical Workflow Solutions (CWS)
    ------------------------------


  • 2.  RE: To break or not to break the JAMA Sync after a Project is over?

    Posted 06-19-2018 13:41
    Hi there Sri,

    That's a great question.  At this point, the Reuse & Sync option is pretty labor intensive on our systems and you can definitely see performance issues if you're doing this with a large number of items.  However, if you've just got your items linked with a global ID, that should be a bit easier than constantly reusing and syncing.

    Additionally, you mention reviewing best practices for this feature and we've actually got a great article published here that covers exactly this.

    And finally, you mention restricting permissions on a sync and I'm wanting a bit more context on this to better answer it.  Are you looking to restrict permissions for who can trigger a reuse & sync or for what is reused and synced or what?

    Thanks again and I'll keep an eye out for that response about the permissions portion of your request!

    ------------------------------
    Nick S
    Jama Software
    ------------------------------