Open h-m-f-t opened 3 months ago
@h-m-f-t what's the reasoning for the blocked by tickets?
@abroddrick I wasn't sure if those were pre-req's or not, particularly given my examples. What say you?
@h-m-f-t Sorry I missed this!
To reply to your question in TLDR: No, we wouldn't need the states to change we just need to use audit log for what is shown in the example
My original explanation: What is shown in the example is easier done with just using the audit logs completely to figure out what has been changed and removed. For instance, a domain invitation being"canceled" would then require us to look domain invitations that were deleted. For "deleted domain managers", we would just look for UserDomain roles deleted for this domain. We don't actually need the state changes to show this, in fact that makes the suggested design a bit harder to do if we are using three tables and not just one.
However, I think no matter what this may slow down the domain's page loading, especially for domains that have had a lot of minor updates. What if we had this just be a link and the link redirect you to a new page that shows what you described (with button to go back). That way we don't add lag when this feature is not always needed.
Issue description
As a analyst I want to see all actions that have been taken on a domain, who took them, and when So I can quickly get up to speed on a given domain and offer better support to registrants
Acceptance criteria
Domains
, add an expandable activity history (collapsed by default) of recent [how recent? what about all?] activity that affects a domainAdditional context
Here's an example of how this might look:
Links to other issues
1604
1606