Comments
-
As Vidic says, it was introduced in 2.1... there is no version with this functionality that supports 5.0.x.
-
It just loads a page in an iframe - currently for me it points to: http://docs.atlassian.com/confluence/docs-35/whatsnew/iframe So you could take a copy of that page to your local confluence instance, adjusting links as necessary, then find that link in your installation above and adjust it to point to your modified page.
-
componentManager.getJiraDurationUtils().getFormattedDuration(remaining) Well, that will convert a long to days based on the information you have put into timetracking. To get working days between two dates you might need to dig into the greenhopper config, where you can specify what are not working days.
-
I don't have much, but I would advise setting:set GIT_CURL_VERBOSE=1then running the git command. You can post the output up here. Also compare it the output from one of the working users/machines.
-
You do not use SSH keys, so that implies all push/pull etc is over https?
-
No, you cannot. I think Jo-Anne is referring to the script runner plugin which has a "scripted field" type, where you can define the calculation in a line or two of groovy. It can also be done with the behaviours plugin though, although the former is the better option.
-
Similar question: https://answers.atlassian.com/questions/172275/plugins-which-are-used-not-used
-
Standalone jira ships with Apache Tomcat, not the Apache web server. So if you want php you need to install the apache web server yourself. There are lots of good pre-configured LAMP stacks out there...
-
AJS.$("#customfield_10001").closest('div.field-group').hide()
-
Use the Confluence CLI - you can list pages, add labels to pages etc.
-
this will be in the next major release
-
I created it: https://jamieechlin.atlassian.net/browse/GRV-430
-
Pretty sure this has been discussed before, but can't find it now. The date panel is limited to system dates and custom fields that use the marker interface com.atlassian.jira.issue.fields.DateField. I can't do that because it will always show in that panel regardless of whether it's a date or not. I can't right now think…
-
I don't think so... they can download as excel, and there is a parameter in the URL that you can override to get all results, but only works for the excel view.
-
Rambanam's answer is for a plugin, for a script get a labelManager like: def labelManager = ComponentAccessor.getComponent(LabelManager.class) You will get better help if you post less text, and use the formatting tools for the code and stack trace.
-
Try passing a set if that's what it wants, eg: ["TestLabel"] as Set instead of "TestLabel"
-
Not really, but thanks ;-)
-
That's why I always say to use the safe navigation operator in this case: cfValues['Name of custom field']?.value == null
-
Assuming it's a single select I think you want something like: cfValues['Name of custom field'].value != 'Please select a value' cfValues is always indexed by field name, not field ID. So what you you see in the web UI.Use *.value.contains(...) when it's a multiselect.But, addinglog.warn (cfValues['Name of custom field'])…
-
You don't need to actually use the scripting functionality to get all the other stuff, ie jql functions, workflow functions etc.
-
Script runner (free) has similar functions: subtasksOf, parentsOf. You might find that the script runner versions are significantly faster than the other ones.
-
It depends which field that behaviours on - to me it looks like it should be put on all each of the fields that govern whether death is required.
-
It's some other problem... it will give you the values on the screen, not the ones saved on the issue.
-
Read https://scriptrunner.adaptavist.com/latest/jira/releases/UpgradingToJira7.html and https://scriptrunner.adaptavist.com/latest/jira/#_providing_type_information Also as people say, the context where you are running stuff defines what is available, eg whether issue is there or not.
-
actually ignore that, just run the script in the wiki page alone, that should set the level to debug.
-
It should be:log.getLogger("com.onresolve.jira.groovy").setLevel(Level.DEBUG)
-
https://jamieechlin.atlassian.net/wiki/display/GRV/Getting+Help#GettingHelp-Supportrequests under logging section
-
Most likely a proxy issue... check your system properties from the previous installation. http://www.downforeveryoneorjustme.com/marketplace.atlassian.com/
-
No worries. How about an upvote or two for the comment and answer... ;-)
-
Try replacing with this section. Also I don't see any point in reindexing the parent issue. boolean wasIndexing = ImportUtils.isIndexIssues();ImportUtils.setIndexIssues(true);indexManager.reIndex(newIssueGv);SubTaskManager subTaskManager = componentManager.getSubTaskManager()subTaskManager.createSubTaskIssueLink(issue,…