/
IMPORTANT - Deprecation of Some Fields

IMPORTANT - Deprecation of Some Fields

Owned by Marin Varvodic
Last updated: yesterday at 9:31 am
3 min read

Over the past two years, we've developed numerous fields within the Forge framework. While some have been highly successful, others have been underutilized. To continue delivering value and enhance our offerings, we are streamlining our field suite to focus on more innovative and beneficial features. Thank you for your understanding and support as we prioritize improvements that matter most.

Recently, Atlassian has rolled out significant enhancements to the Forge framework. Despite early challenges, the platform has evolved substantially, enabling more robust and effective app development. To align with these advancements and concentrate on high-impact features, we have decided to streamline our field suite.

Deprecated fields

We are updating our product suite to improve functionality and efficiency. The following fields are set for deprecation:

  • Issue Update → While this field offers insights into who last updated a ticket and when, Jira already includes a native field that provides this information more effectively. The native field automatically updates in the issue navigator, ensuring accuracy and enhanced reporting capabilities without manual refreshes.

  • JQL Filter Fields → This field lacks clear use cases and does not provide the unique, ticket-specific data expected from custom fields. Its functionality, more suited to reporting metrics, fails to justify its existence as a distinct field within Jira.

  • JQL Progress Bar → The output from this field is consistently uniform, negating its intended purpose of showing varied progress. Given its limited utility and the potential complexity of making it more effective, we have decided to retire this field.

  • True/False → This dynamic field, with hardcoded values, presents practical challenges and inconsistencies. We plan to replace it with a more user-friendly BOOLEAN field that incorporates a simple toggle mechanism, similar to those in Jira Product Discovery, which allows for inline editing and aligns better with current user workflows.

  • Commented Fields → Dynamic commented fields have been deprecated due to their complex configuration requirements, mixed data types that reduce clarity, and overlap with existing Atlassian features.

Reasons for deprecation

  • Overlapping functionality → Atlassian has introduced similar functionalities natively within Forge, rendering some of our custom fields redundant. These native features are more integrated and supported, making our versions less necessary.

  • Framework limitations → We've encountered persistent limitations within the Forge framework that hinder our ability to innovate and implement new improvements in certain fields. This has necessitated a reevaluation of our offerings to focus on more feasible and impactful features.

  • Low usage metrics → Analysis of usage data reveals that some fields are seldom used by our customers. Deprecating these lesser-used features will allow us to reallocate resources towards developing new and innovative solutions that meet the evolving needs of our users.

Impact on Fields customers

Here's what you need to know:

  • The deprecated fields can no longer be created. However, if they are already in use, they will remain visible in the Issue View.

  • Eventually, these fields will be completely removed from the system. We are planning this step carefully to ensure minimal disruption.

  • No data loss will occur due to these changes. The fields being deprecated are populated based on existing data in Jira, so removing them will not eliminate any of your stored data.

  • If these changes significantly impact your workflow, we encourage you to book a call with our technical team for support and to explore alternatives.