Comments
-
Please see here - https://answers.atlassian.com/questions/10392768
-
from the docs - openSprints() Only available if you are using JIRA Agile. Search for issues that are assigned to a Sprint which has not yet been completed. (Note that it is possible for an issue to belong to both a completed Sprint(s) and an incomplete Sprint(s).)
-
HI Esther, I was facing an exact same problem which you are facing. Here's how I fixed it (with help from script runner plugin) I had to free up the older project key "GREP" which was now "DSIT" 1) I copy the project and issues of DSIT to an temporary project with key "DSITEMP" 2)I deleted the DSIT project (only by…
-
it was a caching issue.
-
You will have to fetch and check for custom field value. import com.atlassian.jira.component.ComponentAccessor; def customField = ComponentAccessor.getCustomFieldManager().getCustomFieldObject("customfield_10259");// here replace the ID with ID of your custom field. def value =…
-
In the script runner post-function options there is built-in script to "create sub-task", in that post-function there is a section called "Additional issue Actions", in that section you can add a script like def cf = customFieldManager.getCustomFieldObjects(sourceIssue).find {it.name == 'Name of…
-
There might be one of these reasons given in the docs - An issue will only be visible in Plan mode if: * the issue is not a Sub-Task; * the issue matches the board's Saved Filter (see Configuring Filters); the issue's status maps to one of the board's columns (but not the 'Done' column);and there is at least a status being…
-
Hi Viðar, I agree with you, but for large companies having JIRA installations I still feel that 5.211 isn't that old since JIRA 6 only came out in May last year and JIRA 6.x has a majorly overhauled UI in comparision to 5.x but internal APIs haven't undergone drastic changes. I was hoping for 5.x support but I guess I…
-
I will suggest you to create your own REST end point using the script runner plugin or the REST plugin module and use the Java API of the script runner to fetch the details of the dashboard gadgets.
-
From the docs- A dashboard item is similar to a gadget, in that it provides discrete dynamic content that a user can use to customize their dashboard. However, dashboard items use modern rendering technologies like AMD, Soy, LESS, etc. Dashboard items are also able to share web-resources, which greatly improves page load…
-
Instead of URL I would rather use the JQL query directly <ac:parameter ac:name="jqlQuery">project = CONF AND FixVersion=5.8 </ac:parameter>
-
what is your question?
-
Hi Tim, Yes, just make sure you have well defined groups, and customize the permission schemes of your projects and map the scheme to correposding groups. Cheers, Tarun
-
Hi Tim, JIRA already is equiped with pretty advanced group management, if you put all your external users in a certain group and make sure those groups don't have permissions for read/write for your internal projects, wouldn't that fix your problem? Cheers, Tarun
-
Please see here - https://answers.atlassian.com/questions/141382
-
From the docs "Place this as the last post-function, or at least after the Fire Event function. If you don't do this, it won't work."
-
1) Stop jira 2) follow the instructions here -->https://confluence.atlassian.com/display/JIRAKB/JIRA+is+Locked 3) Restart and REINDEX.
-
You can use https://marketplace.atlassian.com/plugins/com.googlecode.jira-suite-utilities/versions#b124 there is a ValueField in the workflow available which can be used to show/hide transitions based on issue types.
-
Oh yes, Indeed, I missed the "jira-cloud" tag
-
In your code in order to get the sub-tasks of an issue you should try issue.getSubTaskObjects(), it returns a collection of "Issue" and it should work. I think you are trying issue.getSubTasks () but this returns List<GenericValue> and is deprecated. and this also requires the subtask objects to be cast to Issue type in…
-
One of the comments "Please provide this issue at your earliest convenience. We absolutely need it provide WIP limit for Expedite swimlanes."
-
Hi Karl, It's indeed an important feature to have WIP for swimlanes, but currently it isn't possible, please vote here - https://jira.atlassian.com/browse/JSW-3681 and see the comments as well.
-
Can you please try enabling/Disabling the plugin from the admin section of "Manage Add-ons"
-
Are you fields present in the custom field section, can you make sure they are available on the screen and field configurations as well.
-
Scripted calculated custom field is the only way for this requirement.
-
For your first query - "is there a possibility, to set up filter that I get for example the average SLA time from all issues last month?" I have implemented something similar, I will suggest you to try the Python REST JIRA client https://pythonhosted.org You can write a JQL to fetch all issues and then store their SLA in a…
-
You can use one crowd license and map the different JIRA and confluence instances as applications in the Crowd Admin console, but the accumulated number of users would count towards the crowd license.
-
I won't suggest you to do XML format backup, full DB backup and restore should be done for production. XML backups are generally done for some lightweight testing wherein data consistency isn't of extremly high priority.
-
Hi Mohin, First of all take backup of your data, also if you are using lot of plugins and their customization in your JIRA then it's a very high chance that you run into compatibilty issues as JIRA 6.x has very diff. APIs and design guidelines as compared to 4.x, thus while installaing the jira 6.x choose the upgrade…
-
Hi Nic, As you have stated - The numbers you've given imply that you need to do some housekeeping and look at your business processes (1277 custom fields and 200 workflows is often a big red flag that things are disorganised), but they don't cause any upgrade related concerns I completely agree with you, but at the same…