[JIRAALIGN-1884] Audit Logs: Don't Capture Allocation Updates From Team Level or Sprint Level

Issue Summary

Audit Logs at both team and iteration level – Need to see specifically the name of the user who was added/removed/changed, role, allocation %, and date it occurred.

Iteration level: Also need to know if the info was copied from the team level or entered directly into the iteration

Team level - if user is added at the iteration level, today they are automatically copied to the team. Need to know it was created at team because of this use case.

Steps to Reproduce

1. Step 1 - Modify allocation at the team level
2. Step 2 - Check audit log
3. Step 3 - Modify allocations at the sprint/iteration level
4. Step 4 - Check audit log

Expected Results

Audit logs for team panel allocations should show which user was affected: 

• By [User name that made edit], on  [date] [time edit was made].
• Team allocations updated - 
• Dev allocation for [Team member name], [Team role]- from [x]to [y] ; Defect allocation for [Team member name] - from [x]to [y] 

If a user was added to a sprint, in the team panel audit log show:

• By [User name that made edit], on [date] [time edit was made].
• Team member(s) added on sprint [sprint name] - 
• Users: [User added]

If a user was removed from a sprint, in the team panel audit log show:

• By [User name that made edit], on [date] [time edit was made].
• Team member(s) removed from sprint [sprint name] - 
• Users: [User added]

If a user was added to a sprint, in the sprint panel audit log show:

• By [User name that made edit], on [date] [time edit was made].
• Team member(s) added to sprint - 
• Users: [User added]

If a user was removed from a sprint, in the sprint panel audit log show:

• By [User name that made edit], on [date] [time edit was made].
• Team member(s) removed from sprint - 
• Users: [User removed]

If a user was deactivated, in the team panel audit log show:

• Team member(s) removed from team - 
• Users: [User removed]

Actual Results

It isn't shown nor is it clear where the allocations were updated and what allocation was changed 

Workaround

No workaround for this issue.