/?php print $breadcrumb; ?>
/?php if ($title): ?>
/?php endif; ?>
Known Issues and Limitations of the Accept360 connector:
- Users cannot view and edit custom fields - in REST the XML is malformed (no starting "<" for custom attributes)
- It is not possible to search for tasks/entities
- Bidirectional associations cannot be created
- Users cannot create subtasks/related entities (ie: not possible to assign a new task to requirement)
- Tasks are not marked resolved when they are 100% complete
- Logical operators reset every time a user amends a query (ie: making a change to an Accept query which is setup with OR relship betwen predicates, resets them to AND)
- Error "Task Submission Failed" occurs when submitting certain Accept 360 requirements. Hower, the change is actually submitted (refresh the task to check)
- Accept connector does not display proper values for some attributes (e.g. a Defect's Severity) due to API limitation, but only internal identifiers. Those fields are therefore hidden.
Possible Future Enhancements:
- Ability to track time with Tasktop's time reporting
- Access to rich content
- Use of Accept360 with Tasktop release planner
- Addition of Custom attricute editors
- Support custom types (types other than Requirement, Defect, Task) in Accept Connector






