Let ISAR generate IsarTaskId #1888
Labels
backend
Backend related functionality
database-change
Will require migration
improvement
Improvement to existing functionality
Have the IsarTaskId for MissionTasks be generated by ISAR and reported back in the response when calling the start-mission endpoint in ISAR.
Similar to what is now done for IsarMissionId and IsarInspectionId.
This might require some refactoring, to have one object type be sendt to the ISAR insance (the mission request or specification), and one object instansiatied when the response comes back from ISAR.
The text was updated successfully, but these errors were encountered: