As of JIRA 5 the Advanced Settings will show a new, unset Option called:
(Which is set in constant JIRA_OPTION_ENABLED_DARK_FEATURES)
What does this mean and what is it for?
Some "dark forces from the other side"? :=)
Well, I switched it to true, but sadly it doesn't turn on a dark web-client theme. :-(
I've been slowly adding to a "dark" web-client theme to make Jira, Bitbucket, and Bamboo. It's pretty good so far, but could always use improvement. I'd gladly welcome any help on it. It uses the Stylus plugin, for Chrome on my desktop. But, it is also available for other browsers. Here is the theme if you interested.
I think they are "labs" features... you could set them through system properties, or I guess globally in the UI.
Here are a couple of examples...
The second one is a bit self-explanatory, you'd have to experiment or look at the code to see what #1 does.
Nope, it is Star Wars day. But yes, it's a real option. I'd be interested to know how you get on - from what I've seen, it's either something to do with users being able to enable/disable functions for themselves, or possibly something to do with renering.
Just found a darkfeatures-panel.vm:
##disable_html_escaping() TODO REENABLE #* @vtlvariable name="textUtils" type="com.opensymphony.util.TextUtils" *# #* @vtlvariable name="isAdmin" type="boolean" *# #* @vtlvariable name="globalEnabledFeatures" type="java.util.List<com.atlassian.jira.config.CoreFeatures>" *# #* @vtlvariable name="userEnabledFeatures" type="java.util.List<com.atlassian.jira.config.CoreFeatures>" *# <div class="module isolated"> <div class="mod-content"> <form class="aui" action="EditDarkFeatures.jspa"> <section id="global-dark-features"> <h3>Site-wide Dark Features</h3> <p> These dark features are enabled for the entire site. ## TODO - copy site dark-features admin from Confluence too, and link from here for admins. ## #if ($isAdmin) ## <a href="$req.contextPath/admin/darkfeatures.action">Change</a> ## #else They may only be disabled by an administrator. ## #end </p> <ul> #if ($globalEnabledFeatures.size()) #foreach($feature in $globalEnabledFeatures) <li> $textUtils.htmlEncode($feature) </li> #end #else <li> No global dark features enabled </li> #end </ul> </section> <section id="user-dark-features"> <h3>User Dark Features</h3> <p> These dark features affect you only: </p> <ul> #if ($userEnabledFeatures.size()) #foreach($feature in $userEnabledFeatures) #set ($featureStr = $textUtils.htmlEncode($feature)) <li> $featureStr ## This could use an XSRF token... worth it? E.g. &amp;#url_xsrfToken() (<a href="EditDarkFeatures.jspa?action=remove&featureKey=$featureStr">remove</a>) </li> #end #else <li> No user dark features enabled </li> #end </ul> </section> <div class="field-group"> <label for="feature-key">Enable dark feature:</label> <input id="feature-key" type="text" value="" name="featureKey" class="text"> </div> <div class="buttons-container content-footer"> <div class="buttons"> <input type="submit" value="Submit" class="button"> </div> </div> </form> </div> </div>
So it looks like there is a EditDarkFeatures.jspa somewhere out there ;)
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs