[MGNLPER-47] Clean up operations and requests Created: 24/Aug/18  Updated: 21/Sep/18  Resolved: 10/Sep/18

Status: Closed
Project: Periscope
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Improvement Priority: Neutral
Reporter: Cedric Reichenbach Assignee: Cedric Reichenbach
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Documentation update required:
Yes
Date of First Response:
Epic Link: Periscope back-end MVP
Sprint: Basel 154, Basel 155, Basel 156
Story Points: 5

 Description   

Currently, the usage and PeriscopeOperation and PeriscopeOperationRequest are too convoluted and confusing. Simplify those things; some ideas:

  • Detach ImperativeOperationRequest from other OperationRequests
  • Drop OperationRequest and merge functionality into Operation


 Comments   
Comment by Saimir Gasa [ 27/Aug/18 ]

creichenbach, given that this issue was included in this sprint, could you please give it an estimate?

Generated at Mon Feb 12 10:28:13 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.