...
Non-issue entities creation.
TFS4JIRA cannot create artifacts that are not issues. This list includes components, users, sprints.Comment deletion/edition. - At this moment we do not store revision of comments and its state. Only the amount and which comment was synchronized.
Meeting requirements of workflow conditions/validators.
TFS4JIRA cannot read upfront limitations of workflow and override them. If some condition is set up on a workflow, REST API has to abide by it as well.Fill fields on transition screens.
We use create issue screens and edit issue screens only.
Azure DevOps limitation
Test cases outcomes.
As test outcomes are not workitems and are not field values also, they are not covered by the fetching mechanism.Setting up the reason “Reason” field.
This field is highly dependant on the workflow and preceding status.