Details
-
Story
-
Status: Resolved
-
Major
-
Resolution: Done
-
None
-
Application version: 7 and 8
Platform versions: Server and DC
Test with the minimum version of Automation for Jira with third-party integrations. (Define this version @afro)
-
R6.4.0 Sprint 1, R6.4.0 Sprint 2, R6.4.0 Sprint 3
-
Description
Xporter integration with Automation for Jira App
Xporter should add a new action on Automation for Jira:
This new action will allow adding:
- Template (Based on the new scope)
- Output Format
- Filename
- Actions List
Xporter will allow the following actions:
- Send Email
- Upload File
Automation for Jira is available on global administration and for each project. This means, if we are on the project level, Xporter will load only templates who belong to the current project.
Furthermore, we will have a new scope for the templates who will appear on Automation for Jira.
ACs:
- When a new action is created:
- Global templates must appear on Global and Project config
- Global + Project templates must appear on the project level
- On the project level, only appear project templates if the XPorter is enabled for the current project.
- The output format must be based on the selected template.
- The filename extension must be validated and autocomplete must be available.
- Actions:
- CRUD operation over post actions.
- Only Upload and send w-mail will be available.
- When SMTP is not configured and warning must be shown.
- When there are no File servers, a warning must be shown.
- CRUD operation over post actions.
- When an action is edited:
- Unexistent data must be validated:
- Templates
- Add an error message saying that the template does not exist.
- The template must be empty.
- File servers
- Add an error icon with an inline dialog saying what's happening.
- SMTP
- Add a warning icon with an inline dialog saying what's happening.
- Action must be saved just when the errors found were solved.
- Templates
- Unexistent data must be validated: