# Feature OP-19500 - Dynamic scripted fields for external system data (such as ScriptRunner)

Project: OpenProject
Status: new
URL: https://community.openproject.org/work_packages/OP-19500

## Planning

| Attribute | Value |
| --- | --- |
| Date |  |
| Priority | Medium |
| Target versions | Wish List |
| Sprint |  |
| Backlog bucket |  |
| Votes | 1 |
| 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 | Modules and project features / Work packages, Administration / Custom fields |
| Feature Flag |  |
| Requires doc change | No |
| Enterprise plan |  |

## Details

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

## People

| Attribute | Value |
| --- | --- |
| Assignee |  |
| Accountable |  |
| Product manager |  |
| Feature Lead |  |
| Developers |  |
| Designer |  |
| Ordered by |  |
| Signed off by |  |
| Interest by |  |

## Estimates and progress

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

## Description

**As** an OpenProject administrator in a large IT project environment  
**I want to** configure dynamic scripted fields that can retrieve, calculate, and display data from external systems  
**so that** work packages can show relevant live or calculated information, such as Jenkins job status, without manual updates or custom development per use case.

<figure class="image op-uc-figure"><div class="op-uc-figure--content"><img class="op-uc-image" src="/api/v3/attachments/921951/content"></div><figcaption class="op-uc-figure--description">This is an example of ScripRunner displaying the Jenkins status in Jira.</figcaption></figure>

This feature request relates to the existing Epic **“Analyze use cases of ScriptRunner”** [**(SJF-51)**](https://community.openproject.org/projects/SJF/work_packages/SJF-51/activity) and reflects a key use case currently covered in Jira via ScriptRunner: dynamic fields, scripted fields, and automation-driven field behavior.&nbsp;  
See: [https://marketplace.atlassian.com/apps/6820/scriptrunner-for-jira](https://marketplace.atlassian.com/apps/6820/scriptrunner-for-jira)

**Acceptance criteria**

*   Admins can define dynamic fields for work packages.
    
*   Dynamic fields can display calculated or externally retrieved values.
    
*   Example use case: If a Jenkins job exists for a work package, the Jenkins job status is shown automatically.
    
*   Field behavior can be configured based on work package attributes, project context, or external data availability.
    
*   Dynamic fields can be added to work packages as custom fields, which can then be reused across projects.
    
*   Errors or unavailable external data are handled gracefully.
    

**Technical notes**

*   Integration logic should support external systems such as Jenkins.
    
*   Configuration should be manageable by administrators.
    
*   Security, performance, and caching should be considered for external data lookups.
    
*   This should build on the analysis already started in [**SJF-51**](https://community.openproject.org/projects/SJF/work_packages/SJF-51/activity).
    

**Permissions and visibility considerations**

*   _To whom is this feature visible?_
    
    *   Administrators configuring the dynamic fields.
        
    *   Project members viewing work packages where the field is enabled and visible.
        
*   _When is it not visible?_
    
    *   If the (custom) field is not configured for a specific work package type.
