412
Customers have installed this add-on in at least 412 active instances.
    by Frank PolscheitAtlassian Verified
    Frank Polscheit is an Atlassian Verified vendor. Verified vendors demonstrate Atlassian standards for add-on quality, reliability, and support.

    Learn more

    for JIRA Server 7.0.0 - 7.2.5 and more versions
    Versions available for JIRA Server 6.0 - 6.4.14
    Unsupported
    This add-on isn't formally supported, but you can ask a question via Atlassian Answers.

    Ask a question

    Supported
    Frank Polscheit supports this add-on.

    Get support

    Data Center
    This add-on is compatible with the clustering and high-availability capabilities of our products.

    Project management and stakeholder awareness is people business, but yellow/red lights help to escalate ... focus your attention

    Project management and stakeholder awareness is people business, but yellow/red lights help to escalate ... focus your attention

    Approach

    Basic Features

    Dynamic rules for automation

    You can configure new traffic-light custom fields setting options to "green", "yellow" and "red". Just select a proper option for each issue, manually. The purpose is NOT to replace any human by an intelligent algorithm.

    Display traffic-lights fields (criticality) for each issue.

    Edit criticality from "green", "yellow" to "red" by a single select list.

    Extend JIRA's search result by your traffic-light columns to sort and get an overview.

    Specify dynamic rules, which are highly flexibel to treat complex circumstances. Using them within a JIRA listener or workflow function, you can set customfields to any traffic-light value you want, automatically.

    More details

    Create new custom field(s) as traffic-light. Since v2.0.2, all necessary options are automatically created (red, yellow, green). Since v2.0.5, additionally "amber" and "pink" are provided for escalations.

    You can define complex statements taking all issue methods into account, from current issue status until issue's parent object or status of children to determine, what traffic-light status to set: just program your rule in javascript syntax!

    Available Listeners:

    • de.polscheit.jira.listener.DynamicRulesUpdateListener
    • de.polscheit.jira.listener.DynamicRulesCreationListener
    • de.polscheit.jira.listener.DynamicRulesWorkLoggingListener

    The following utility functions are available:

    • log(Object obj);
    • setCFoption(MutableIssue issue, String customfieldName, String value);
    • getCF(MutableIssue issue, String customfieldName);

    WARNING:

    Exceptions are put into the JIRA log file. There is no syntex or semantic checking! So, be sure to enter the correct expression as admin.

    frank@polscheit.de

    User reviews

    (13)
    Sign in to write a review »
    by Aurelia Hibbert on 2014-10-03
    Excellent plug-in. Easily compatible with other custom fields and helpful, speedy support as well! Impressive all-round.
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Frantisek Kall on 2013-04-10
    This plugin is very useful, especially for reporting and management view. Quick and efficient support from the developer Frank. Exceeded our support expectations. Highly recommended.
    Was this review helpful?YesNo
    by Roland Müller on 2013-02-16
    This is a great little plugin that also allows setting the traffic light status based on time tracking values automatically. The new version 1.2.7 now supports a listener for logging time. Developer answers very fast, and did release this version in less than a week after some proposals from our side. It also works together with Tempo time tracking. Using javascript for the listeners required some lookups in the issue rest API docs in order to get the data types right. Example: var t=issue.getTimeSpent().longValue(); var m=issue.getOriginalEstimate().longValue(); var c=(t<m)?'green':'red';util.setCFoption(issue,'Criticality',c); Thank you for this plugin, Frank!
    1 out of 1 found this review helpful
    Was this review helpful?YesNo
    by Tianhao Li on 2012-06-27
    This plugin is awesome especially for reporting which meets our requirements. I am wondering if I add the extra color amber and pink to the dropdown list, why it doesn't work for amber color, however it displayed the same color as yellow? For pink it is OK just a "!" on the color. Thanks for your help.
    Was this review helpful?YesNo

    Frank Polscheit

    According to another user, they wished the color name "amber" as alias for "yellow": both are functionally identical. The intension of "Pink" is an escalation one level above "red"!

    by Matthew Cobby on 2012-04-12
    It's a good plugin which provides something a lot of our teams are using but it's a little inconsistent. We are upgrading our Jira and upgrade this plugin from 1.1.1 to 1.2.3 and somewhere along way the plugin key has changed: Original Key: de.polscheit.jira.plugins.traffic-light_status:traffic-light_status New Key: de.polscheit.jira.plugins.trafficlight:trafficlight-status This means that the old customfield can't find the plugin and none of the resources works. The only solution for most users would be to delete the custom field and re-install. However, this means that all your existing filters and dashboards will be broken and you have to re-add the new custom field. If you are a little more confident, you can open up the plugin and edit the atlassian.xml file to restore the plugin key & associated references to their original value. If you want to know more, contact me on matt (at) andamooka.com
    Was this review helpful?YesNo

    Frank Polscheit

    Sorry for that inconveniece during the refactoring between version 1.1.x and 1.2.x having a lot of internal changes. The current plugin key will stay stable and unchanged in the future. 

    Regards,
    Frank 

    Pricing

    Pricing details are loading…

    Paid-via-Atlassian pricing FAQ

    How does server add-on pricing work?

    Server products and add-ons 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 add-on licenses at any time. Upgrade prices are calculated based on Atlassian's formula (view example).

    If add-on 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 tier?

    For JIRA Server 7.0 or later, the add-on tier should match the maximum tier of the licensed JIRA applications 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 add-ons.

    For versions of JIRA Server prior to 7.0, the add-on tier should match the licensed user tier for JIRA. Even if fewer users want to use the add-on than your JIRA license, the two licenses should match exactly.

    Do you offer academic, community, or open-source licenses?

    For server add-ons, purchase and renewal is half-price if you have an academic license for your Atlassian host application. Server add-ons are always free for community and open-source licenses. Cloud add-ons do not have discounted or free licenses.

    For more details about qualifying for special licenses, see here.

    Can I extend my free trial?

    For server add-ons, you can extend your add-on 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 add-on listing in UPM from your Atlassian host application, and you're all set.

    How can I buy add-ons 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 add-on pricing is no longer available. You have two options for add-on purchasing:

    • Purchase the add-on at the non-legacy Unlimited (10000+ users) tier.
    • Renew your JIRA or Confluence license at a non-legacy tier, then purchase the add-on at the same tier.

    Learn more

    Support

    Frank Polscheit is Atlassian Verified. Verified add-on vendors demonstrate high quality, reliability, and business traction. Learn more

    Frank Polscheit - Solutions & IT-Consulting supports Traffic-Light CustomField for JIRA. You can visit the support site to get help.

    Get support

    Versions

    Version 2.0.10-JIRA7 JIRA Server 7.0.0 - 7.2.5 Released 2016-11-08

    Summary

    bug fix of large icon images when exporting etc.

    Installation

    1. Log into your JIRA instance as an admin.
    2. Click the admin dropdown and choose Atlassian Marketplace. The Manage add-ons screen loads.
    3. Click Find new add-ons from the left-hand side of the page.
    4. Locate Traffic-Light CustomField for JIRA via search. The appropriate add-on version appears in the search results.
    5. Click Try free to begin a new trial or Buy now to purchase a license for Traffic-Light CustomField for JIRA. You're prompted to log into MyAtlassian. Traffic-Light CustomField for JIRA begins to download.
    6. Enter your information and click Generate license when redirected to MyAtlassian.
    7. 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 Traffic-Light CustomField for JIRA versions compatible with your instance, you can look through our version history page.

    Similar add-ons