# Feature JIM-238 - Force testing Jira configuration before saving

Project: Stream Jira to OpenProject data Migrator
Status: in specification
URL: https://community.openproject.org/work_packages/JIM-238

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | 18.0.0 |
| Sprint |  |
| Backlog bucket |  |
| Votes |  |
| List |  |
| Roadmap |  |
| Relevance |  |

## OPEN POINTS / FEEDBACK

_No work packages_

## Features and Chunks

_No work packages_

## Bugs and other work packages

_No work packages_

## Technical Details

| Attribute | Value |
| --- | --- |
| Module | Integrations / Jira |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

| Attribute | Value |
| --- | --- |
| Pull preview |  |
| Mockups |  |
| Accessibility | No |

## People

| Attribute | Value |
| --- | --- |
| Assignee | Alfonso Mancilla |
| Accountable |  |
| Product manager |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

| Attribute | Value |
| --- | --- |
| PD (min) |  |
| PD (max) |  |
| Work |  |
| Labor costs |  |

## Description

Seen during a migration with a customer, the user totally overlooked the test possibility.

The action is a link currently, but it's not visible enough.

Testing should be the call to action. Once clicked, either successful or not, it's possible to save the configuration.

**Acceptance criteria**

*   When creating a jira configuration, the call to action is "Test connection" button
    
*   "Test connection" is disabled if url or PAT is missing. It's enabled once URL and PAT are set
    
*   Once "Test connection" has been clicked and the test result comes back and is displayed, the user can save the configuration
    
    *   \[open\] does it make sense to allow saving if test has failed? I think it does if the user wants to save the information and come back later to edit it.
        
*   The same flow should be followed  for editing.
    

**Technical notes**

*   <br>
    

**Permissions and visibility considerations**

*   _To whom is this feature visible?_
    
*   _When is it not visible?_
    

**Translation considerations**

*   _Key terms and phrases in the key languages_ 
    

**Out of scope**

*   <br>
    

_Set the_ **To be informed/consulted teams** _field to include all teams necessary to be informed of the changes._