Issue Summary

This is reproducible on Data Center: (yes)

Help doc expected behavior is to require the 3 fields as per Jira Integration - Map projects to programs

Map projects to programs

1. To add Jira projects, click Add Project on the Manage Projects tab, and then complete the fields in the table. Use the information you collected in 10X: Jira Integration Data Collection.

• • Project Key: Type the Jira project key.
  • Project Name: Type the Jira project name. Note that if the Jira project name changes, the name displayed in Jira Align will automatically change.
  • Program: Select the Jira Align program your Jira project will map to.

1. Click Save.

However, when the user attempts to utilize one or none of those filters, a success message appears, even though the project has not been synchronized at all.

Steps to Reproduce

1. Create a Project in Jira.
2. In Jira Align, go to Administration > Jira Settings and click on the “Add Button”.
3. Enter data into the Project Key field, leave the Project name field blank, and from the subsequent dropdown menu, select a Program before clicking on save; or skip entering data into the Project Key field, input a Project name, and select a Program before clicking on save; or leave both Project Key and Project name fields empty and click on save
4. Observe that a green pop-up window indicates that the update was successful. Subsequently, upon page refresh, it is noted that the Project is not displayed in the Projects list.
5. Click on the "View logs" button and filter for ‘Configuration’.
6. Notice that, intermittently, the message shown In the UI logs, Jira Project Added - XXX is displayed, being "XXX” an incremental number

Expected Results

As the three fields are expected/required when using two of those, a red pop-up is expected to appear and inform the user that all fields are required in order for the sync to occur

Actual Results

When the user attempts to utilize two of those filters or no data at all in the fields, a success message appears, even though the project has not been synchronized.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available