| Package | Description |
|---|---|
| com.playsql.requirementyogi.ao |
Database objects - We rely on Atlassian's ActiveObjects specifications.
|
| com.playsql.requirementyogi.ao.upgradetasks |
Upgrade tasks.
|
| com.playsql.requirementyogi.ao.v33 |
Model beans for the database tables.
|
| com.playsql.requirementyogi.api.dev |
APIs which are only available at development time, for internal testing purpose.
|
| Class and Description |
|---|
| AOBaseline |
| AOIssueTemplate
A template used in the Jira issue bulk synchronization, to send issues to Jira.
|
| AORequirement |
| Class and Description |
|---|
| AORequirement |
| AORequirementLink
Beware of this entity.
|
| Class and Description |
|---|
| AODependency
Dependency between two requirements:
- When REQ1 cites REQ2, there is an AODependency TYPE_ORIGIN on REQ1, and AODependency TYPE_DESTINATION on REQ2,
- When REQ1 is deleted (or its status is), then AODependency TYPE_ORIGIN is deleted and AODependency TYPE_DESTINATION is OUTDATED
- When REQ2 is deleted (or its status is), then AODependency TYPE_ORIGIN is OUTDATED and AODependency TYPE_DESTINATION is deleted
- If REQ2 is in a page, then 1 AOLink is tied, using AOLink.DEPENDENCY_ID = AODependency(TYPE_ORIGIN).ID,
- If REQ2 is in an Excel file, then there is no AOLink.
|
| AOIssueTemplate
A template used in the Jira issue bulk synchronization, to send issues to Jira.
|
| AOProperty |
| AORequirement |
| AORequirementLink
Beware of this entity.
|
| Class and Description |
|---|
| AORequirement |
Copyright © 2020 Play SQL. All rights reserved.