Help get this topic noticed by sharing it on Twitter Twitter, Facebook Facebook, or email.
coconnor
sad I’m anxious
coconnor January 30, 2012 10:13

How can 1 Scrumworks Pro product’s data be recovered without impacting other products ?

I have a question regarding recovering Scrumwork Pro product data.

How can a product administrator, or a global administrator, recover lost, damaged or deleted product data for 1 product without having to recover or change any other product data ?

For example;- In the case when some data from product A is incorrectly deleted, how is it possible for that product administrator to recover that data several days later while keeping all the latest data from all the other products B, C, D, etc unchanged ?

Where, in Scrumworks Pro user documents, can I read more details about how Scrumworks handles this and similar situations ?

We use
ScrumWorks Pro
Version: 5.1.0
Build: 2011-10-28 16:28 r36920
Case ID: SWP1357769

And a MySQL type database stored on a server centrally managed by our IT department. The data on the server is backed up in bulk per standard IT methods.
1 person has
this question +1
Reply

  • Mark Lovell EMPLOYEE
    Mark Lovell (Official Rep) January 30, 2012 18:44
    Unfortunately there really isn't an easy way to do this. One of the best ways, that offers the most recovery for least amount of risk to your existing data is to use the product Import/Export options.

    You would want to setup a "test" copy of Scrumworks with the most recent restored backup of the data that you need to move into your production database on a separate machine.

    Then follow the steps outlined here to export the product in question:
    http://www.danube.com/docs/scrumworks...

    Finally you would then move the newly generated Excel file to your live server and import that data into your production copy of Scrumworks.

    This would allow you to recover the following data from the previous product:

    All custom statuses
    All Sprints
    The Sprint Estimate history. This is the sum of task estimates on the given day. This sum is used in calculating Sprint burndown charts.
    All Releases
    All Backlog Items, in both Sprints and the Product Backlog, including deleted (inactive) PBIs, if estimate history was preserved on delete event.
    The estimate history for each Backlog Item
    Parent history for Backlog Items. This tells you when PBIs were dragged between Releases and Sprints.
    Status history for Backlog Items. There is one change entry for each day the status is changed.
    All data regarding attachments associated to Backlog Items.
    All Tasks
    The estimate history for each Task
    Impediments, both resolved and open
    Comment
    good answer! good answer! (undo)
  • (some HTML allowed)
    How does this make you feel?     Add Image
    I'm

    e.g. indifferent, undecided, unconcerned happy, confident, thankful, excited kidding, amused, unsure, silly sad, anxious, confused, frustrated

    Cancel