...
- In built field syncing of: Summary,Type, Status, Priorities, Components, Affects Version(s), Fix Version(s), Assignee, and Comments;
- Configurable synchronization schedule;
- Configurable synchronization direction options: single (ET to JIRA or JIRA to ET) and bi-directional (ET synchronizes first or JIRA synchronizes first)
- Filter options supported for JIRA to ET synchronization, including JQL fragments;
- Custom field support;
- Support for synchronizing picklist (select list) values from JIRA to ET, including JQL fragments;
- JIRA ID on the incident in ET;
- Remote links to the incident in ET and test run added on the JIRA Issue; and
- Full JIRA workflow transition support from ET.
...
Filtering options include:
- Type
- Statuses
- Priorities
- JQL
- Components
- Affected Versions
- Fixed Versions
If no filter criteria is selected all issues logged in the JIRA project will be in scope for synchronization.
| Info | ||
|---|---|---|
| ||
When using JQL fragments as part of your query criteria, the additional filter criteria you have selected will be added. ET already specifies the JIRA project in the filter parameters based on the project you are syncing your ET project with. If you find that you the issues being synchronized are not what you expected, it is worth testing your JQL fragment in JIRA. |
| Anchor | ||||
|---|---|---|---|---|
|
...