tfsolutions/apps
Apps
Menu

Jira Cloud / Company-managed

Screen Self-Service for Jira

Screen Self-Service for Jira lets existing project admins manage eligible fields themselves. Jira admins choose which projects are enabled and which changes need approval.

Ask about the betaRead the guide (EN)

01From practice

Move a field without a detour through an admin ticket.

Delegate suitable screen changes to existing project admins. Jira admins set the boundaries and retain approval of structural changes.

02Understand a change

See what will change before saving.

Interactive example: choose a screen

Before

  1. Summary
  2. Description
  3. Priority
  4. Environment

After

  1. Summary
  2. Customernew
  3. Prioritymoved
  4. Description

Environment removed. Eligible fields can be added or removed.

Before

  1. Summary
  2. Description
  3. Priority
  4. Environment

After

  1. Summary
  2. Customernew
  3. Prioritymoved
  4. Description

Edit also supports eligible field placements.

Before

  1. Summary
  2. Description
  3. Priority
  4. Environment

After

  1. Summary
  2. Prioritymoved
  3. Description
  4. Environment

View: reorder existing fields only. In V1, additions and removals are limited to Create and Edit.

Illustrative example. Field availability depends on the actual Jira configuration. This example changes no Jira data.

03Approval & execution

Who decides — and where.

  1. Project admin proposesReview the change and affected selections.
  2. App checks configurationPermissions, field rules and shared uses.
  3. Approval according to policyNew screens and screen schemes: a different Jira admin in the admin area. Existing isolated changes: according to the configured policy.
  4. Requester executesThe approved change is executed, verified and logged.

Emails notify admins about pending requests. Decisions happen in the admin area, which remains available when emails are paused.

04Features & boundaries

All current and future issue types are available to select. If other selections use the same screen, the app shows that affected scope before execution.

Choose a project

Enable a project once: all current and future issue types are available, without entering example issue keys.

Review the change

Reorder existing Create, Edit and View fields on one tab. Add or remove eligible Create and Edit fields.

Save or request approval

Compare before and after. New screens and screen schemes need approval from another Jira administrator.

More independence. Clear boundaries.

Current Jira permissions remain authoritative. Groups can further restrict existing project admins. Changes stay traceable, and Jira admins can pause new Jira change steps and approval emails separately.

What the first version supports

For company-managed software and business projects in Jira Cloud. No View field additions, multi-tab editing, direct shared changes across projects, workflow editing or custom-field creation. Jira layouts can affect field visibility. An app-history backup does not restore Jira configuration.

05Inside the app

The actual interface.

App screenshots with synthetic example data. Open an image to view it at full size.

Edit fields in the screen editor
Edit fields in the screen editor
Review structural changes in the admin area
Review structural changes in the admin area
Inspect operations, pauses and backups
Inspect operations, pauses and backups

06Guides & help

Guides, support and policies

The existing app documents below are in English. Their approved text and revision identifiers are unchanged.

App support