Capturing key info during workflow changes
Capturing key info during workflow changes
Post functions available to add/update/delete rows or clear the table entirely. Choose to update top/last row with values from system fields, custom fields, current datetime or current users.
Consolidate associated fields into a single table with configurable columns.
Segregate important details like approvals into a Table custom field for convenient viewing
Possible Use Cases:
- For approval tracking - easy tracking instead of having to reconstruct the changes from the Change History tab.
- For audit tracking - serves as an audit log as it is non-editable and the values populated automatically via workflow post functions.
- Baseline tracking - capture snapshots of important fields at various state of the lifecycle
- Grouping of related fields - A great tool for consolidating since Jira only allows 1 custom field to be displayed per row and the date and user fields are placed in separate panels
The app may help to address the following issues
|10 users$10||25 users$100||50 users$200||100 users$300||250 users$500||500 & upAdditional pricing details|
- How does server app pricing work?
Server products and apps are hosted on your servers. Licenses are perpetual and the purchase price include 12 months of maintenance (support and version updates).
You can renew maintenance after 12 months at 50% of the current purchase price. You can upgrade the tier of your host product and app licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).
If app pricing changes after your initial purchase, there's a 60-day grandfathering period during which you can renew based on the old pricing.
- How do I determine my server pricing?
Apps are billed based on the number of users in your host product. For Jira Server 7.0 or later, the app tier should match the maximum tier of the licensed Jira products on your instance. For example, if you're running Jira Software (50 users) and Jira Service Desk (10 agents) on the same instance, you should purchase the 50-user tier for apps. For versions of Jira Server prior to 7.0, the app tier should match the licensed user tier for Jira. Even if fewer users want to use the app than your Jira license, the two licenses should match exactly.Note: While this app has features specific to Jira Service Desk, the app is technically available across the whole Jira instance. Therefore the above guidelines for the license tier still apply.
- Do you offer academic, community, or open-source licenses?
For server apps, purchase and renewal is half-price if you have an academic license for your Atlassian host product. Server apps are always free for community and open-source licenses.
For more details about qualifying for special licenses, see here.
- Can I extend my free trial?
For server apps, you can extend your app trial up to 5 times - in other words, for up to six months. Extend your trial by generating a new evaluation license key from Atlassian Marketplace. Click Try it free and you'll be directed to generate a new license. Paste this license key into the app listing in UPM from your Atlassian host product, and you're all set.
- How can I buy apps for my legacy Jira Server or Confluence Server license?
If you own a legacy Jira Server Unlimited (100+ users) or Confluence Server Unlimited (2000+ users) license purchased in 2012 or earlier, legacy app pricing is no longer available. You have two options for app purchasing:
- Purchase the app at the non-legacy Unlimited (10000+ users) tier.
- Renew your Jira or Confluence license at a non-legacy tier, then purchase the app at the same tier.
Akeles Consulting provides support for this app.
Version 1.0.0 • Jira Server 7.2.0 - 7.8.1 • Released 2018-02-19
Compatibility for Jira Data Center and Jira Service Desk
- TABLECF-3 - Support Table Custom Fields on JSD customer portal
- TABLECF-4 - Compatibility for Data Center
- TABLECF-5 - Allow Custom Fields Values to be displayed in Table Custom Field
- TABLECF-6 - 'Undefined' column name when all the columns are deleted
- TABLECF-7 - To be able to update (add/replace/clear) a particular row entry based on a matching value
- TABLECF-8 - To be able to delete a row based on a matching value
- TABLECF-9 - Table value is purged if custom field is placed in edit view and issue is edited
For more info, please refer to Release notes for 1.0.0
- Log into your Jira instance as an admin.
- Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
- Click Find new add-ons from the left-hand side of the page.
- Locate Table Custom Fields for Jira via search. The appropriate app version appears in the search results.
- Click Try free to begin a new trial or Buy now to purchase a license for Table Custom Fields for Jira. You're prompted to log into MyAtlassian. Table Custom Fields for Jira begins to download.
- Enter your information and click Generate license when redirected to MyAtlassian.
- Click Apply license. If you're using an older version of UPM, you can copy and paste the license into your Jira instance.
To find older Table Custom Fields for Jira versions compatible with your instance, you can look through our version history page.