Holarch

Plan & Deliver

Project Activity

Every recorded edit in a project, newest first, with who made it, which item it touched and what changed; filter by date, person, class, kind of change and text, and export the list.

How to use it →

On this page
  1. Overview
  2. Concepts
    1. What is recorded
    2. Entries and actions
  3. How to use it
    1. When and why
    2. Find out what changed this week
    3. See every change to one item
    4. Find who changed a value
    5. Export the activity
    6. Worked example: the CubeSat EO-1 demo
    7. Tips and good practice
    8. How it connects
  4. Activity page
    1. Filters
    2. Entries
    3. Top bar
  5. Messages
  6. Limits
  7. Related pages

Overview

Plan & Deliver → Activity lists every recorded edit in the project, newest first. Each entry is one action: the same step that Undo reverses. An entry shows when the action happened, who made it and which items it touched. Open an entry to see each change, with the field, the value before and the value after.

Use Activity to answer "what changed in this project, and who changed it?" without opening items one by one. An item's own History… shows the same records for that item only.

Activity is a change log for working together. It lists edits; it does not count, chart or rank people.

Concepts

What is recorded

  • Items: created, changed (each field, attribute and description, with before and after), deleted and restored.
  • Relationships: added and removed, and changes to relationship attributes such as a suspect-link mark.
  • The person: the name of the account that made the change.

Diagram layout and document formatting are not recorded here. To see how the whole project looked at an earlier time, compare baselines in Baselines & Versions.

Entries and actions

One action can make several changes. For example, creating a requirement and linking it to a function in one step is one entry with two or three changes. The summary names up to three items and the number of changes, for example "Edited R.1 Image Resolution, 1 Capture Imagery · 3 changes".

A single change shows its kind and the fields that changed, for example "Changed R.1 Image Resolution · Name, Description".

How to use it

When and why

Open Activity after a review meeting, after time away from the project, or when a value looks wrong. It shows what the team changed since a date, and who to ask about a change.

Find out what changed this week

  1. Open Plan & Deliver → Activity.
  2. Set From to the first day of the week. You see only the entries made since that day.
  3. Click an entry to open it. You see a table with Item, Change, Field, Before and After.
  4. Click an item name to open the item.

See every change to one item

  1. Open the item and click History….
  2. Click All project activity at the end of the dialog. Activity opens filtered to that item: the chip Item: <name> shows above the list.
  3. Click × on the chip to see every entry again.

The item filter also lists actions that changed the item's relationships from the other end.

Find who changed a value

  1. Type the value, the field or the item name in the search box. The list keeps the entries whose items, fields or values contain the text.
  2. Open the entry to see the before and after values and the person.

Export the activity

  1. Set the filters you need.
  2. Click Export ▾ and choose Activity (CSV) or Activity (Excel). The file holds one row per change of the entries that match the filters.

Worked example: the CubeSat EO-1 demo

  1. Open the demo project and change the description of a requirement, then rename a function.
  2. Open Plan & Deliver → Activity. The rename is the first entry and the description change the second, both under your name.
  3. Choose Changed in the kind of change list and Requirement in the class list. Only the description change remains.

Tips and good practice

  • Combine filters: for example a person and a date range shows what that person changed in a review period.
  • Use Export ▾ to attach the changes of a period to review minutes.
  • To undo a change to one item, use Revert to version in that item's History….

How it connects

  • Baselines & Versions holds the earlier states of the whole project; Activity holds the individual edits between them.
  • Each item's History… shows the item's own records and links here.

Activity page

Filters

ControlWhat it does
FromEntries on or after this day.
ToEntries on or before this day.
Everyone / a nameEntries by one person. The list names everyone who made a recorded change.
All classes and kinds / a classEntries that touched an item of that class.
All changes / a kindEntries with a change of that kind: Created, Changed, Moved, Deleted, Restored or Relationship changes.
SearchEntries whose items, fields, values or person contain the text.
Item: chipEntries that touched one item (from All project activity in its History).

Entries

Each entry shows the date and time, the person and a summary. Click it to expand the changes. Item names are links; an item that is no longer in the project shows in italics without a link. Show 100 more at the end adds the next 100 entries.

Top bar

Restore a Previous Version… brings back an earlier automatic save of the whole project.

Messages

MessageMeaning
No recorded edits yet. Edits to items and relationships appear here as they are made.The project has no recorded changes.
No entries match the filters. Clear a filter to see more.The filters exclude every entry.
Nothing to export: no entries match the filters.Export found no entries to write.
Recorded since <date>.The oldest recorded change the project still holds.

Limits

  • The project keeps its most recent 3,000 to 4,000 recorded changes. Older ones are no longer listed; the note above the list says so when the project is near that size.
  • Diagram layout and document formatting changes are not recorded.