/
Universal Properties Editor for Jira (UPEJ) Guide

Universal Properties Editor for Jira (UPEJ) Guide

Universal Properties Editor for Jira (UPEJ) — User Guide

Who this guide is for

This guide is for Jira admins and advanced users who need to view, create, update, and delete Jira properties without REST scripts.

Supported property types

Universal UPEJ supports all major Jira property scopes in one UI:

  • User properties

  • Issue properties

  • Project properties

  • Issue type properties

  • Comment properties

  • Board properties

Before you start

  • UPEJ app must be installed in your Jira Cloud site.

  • You need Jira permissions for the selected target object.

  • For write/delete actions, your Jira role must allow updates.

  • For Board properties, Jira Software access is required.

Open the app

  1. Log in to Jira.

  2. Open Settings (gear icon) -> Apps.

  3. Open Universal Properties Editor for Jira (UPEJ).

Universal workflow (same for all types)

  1. Select Property Type.

  2. Set the required Target for that type.

  3. Click Load to fetch existing properties.

  4. Run one of the actions:

    • Get (read one key)

    • Set/Create (create or update)

    • Delete (remove key)

Target format by property type

1) User properties

  • Target input: Jira user (account)

  • Use when: you store user-level metadata (profile flags, integration attributes)

2) Issue properties

  • Target input: issueKey (example: APPS-123)

  • Use when: you store issue-level integration state, custom process markers

3) Project properties

  • Target input: projectKey (example: APPS)

  • Use when: you keep project-scoped settings and feature flags

4) Issue type properties

  • Target input: issueTypeId

  • Use when: configuration is tied to issue type behavior

5) Comment properties

  • Target input: commentId (in context of an issue)

  • Use when: metadata must be attached to specific comments

6) Board properties

  • Target input: boardId

  • Use when: board-level settings are needed (Jira Software)

Actions explained

Get property

  1. Enter/select property key.

  2. Click Get.

  3. Review returned value.

Set/Create property

  1. Enter/select property key.

  2. Enter value (usually JSON for config use cases).

  3. Click Save/Set.

  4. Reload and verify.

Delete property

  1. Enter/select property key.

  2. Click Delete.

  3. Confirm deletion if prompted.

Practical examples

Example A: User property

  • Type: User

  • Key: profile.department

  • Value: "Support"

Example B: Issue property

  • Type: Issue

  • Target: APPS-123

  • Key: integration.syncStatus

  • Value: {"status":"done"}

Example C: Project property

  • Type: Project

  • Target: APPS

  • Key: feature.rollout.enabled

  • Value: true

Example D: Board property

  • Type: Board

  • Target: 101

  • Key: dashboard.mode

  • Value: "compact"

Best practices

  • Use stable key naming conventions (domain.subdomain.flag).

  • Prefer valid JSON for structured values.

  • Keep values concise and documented.

  • Reload after each write/delete action to validate result.

Troubleshooting

  • Property not found: verify type, target, and key.

  • Permission error: check Jira permissions and role rights.

  • Invalid JSON/value format: validate value before saving.

  • Board not accessible: confirm Jira Software availability and board access.

Support

If you need help, contact support:
https://moy-apps.atlassian.net/servicedesk/customer/portal/2