Comments
-
JQL is not SQL, it is for finding issues, not telling something what to display. You should be able to construct JQL to find the issues you want to report on, but the real challenge is going to be finding something to show you the data you want from the issues. There is a "time in status" report, which I think will try to…
-
Rajesh is right, empty fields won't come out on word docs.
-
No. You need those two, as they're structural things and not even really fields. JIRA can't store data without them. It's a bit like asking for a cup of tea without using water and tea leaves.
-
For custom fields, you can do this with * Custom field context (only show it in some projects) * Field configurations (hide the field in some configs and use the configs for different projects) * Screens (put it on some screens and not others) It's up to you which one you use, although I'd lean towards screens for your…
-
I've not seen any add-on that will do this, and yes, you're right, natively, it does not happen. For "move to sub task", that would be a nice feature in some ways, although I don't think it's appropriate for Scrum boards in work mode - you should have been grooming the issues into the right shape well before you started…
-
Your source data needs to include a column for the parent issue key, then JIRA will understand that they're under specific tasks.
-
They appear to the left of the Epic column if you have them enabled (i.e. at least one issue has a version set)
-
A sever licence is "perpetual" - your JIRA will continue to work as it did before it expired. There are some minor differences: * You can't raise support requests * You can't upgrade to any version released after the end of the licence * Your admins will see the odd reminder message that you're not supported However, if…
-
This is a bit of a bug-bear in JIRA Service Desk. The problem is that you absolutely do *not* want to move an issue from a Service Desk into a Software project. If you do that, it looks to the customer like you have deleted their JSD request, which is, at best, confusing, and at worst, looks rude and ignorant! There is no…
-
Points 1-3 aren't really good to answer in that discrete order so... JIRA's projects and issues use "schemes" for their configuration. Some schemes are project only (notification, security, etc) and others go down to the issue level. Field configurations are a 2-layer scheme. The first layer (a "field configuration…
-
No, because they could potentially be far longer than the display device can show or run with cleanly. You could hack the core code to display them all after you move to server, but I wouldn't recommend it.
-
Just to clarify something in your question - there is no "integration" or "dependency inclusion". JIRA Software *is* Greenhopper. GH was the first version of it, it got renamed to JIRA Agile after Atlassian acquired it, and then renamed again to JIRA Software as it was turned into an application. You should not include any…
-
There's a few ways to do it. For example: * Have status like "auth 1 -> auth 2 -> auth 3". * Add a simple check list field (with multi-check boxes or an add-on for a bit more power) * Have looped transitions that record authorisations without changing the status until the last one It depends on what you're trying to track…
-
That sounds like you have some form of add-on or UI customisation that is breaking the system field lists somewhere. Do you have the Script Runner enabled, or any javascript hacks in the announcement banner or field descriptions?
-
Get an xml backup of the JIRA you are trying to import from. Create the new project you are going to import things into. Use Admin -> project import to extract the project issues from the backup xml into the new project with all comments, history etc.
-
Attach the design to JIRA and build a workflow that asks for approvals? I don't see a need for add-on tools for that.
-
No, there's no way to do it in the UI, This is because it's mostly useless - people generally don't want swathes of "global" components that are not actually global. (We do want proper global components, but adding the differnet components to projects with the same name is not a global component)
-
I'm not aware of add-ons for either JIRA or Jenkins that would do all of that. You'll need to write something (or dig deeper than I have - I only skimmed the Jenkins ecosystem as I'm not familiar with it) I'd use the ScriptRunner to create a web-fragment and a panel to do the front-end UI, and then a couple of scripts to…
-
See https://confluence.atlassian.com/adminjiraserver073/customizing-email-content-861253783.html You should also check the marketplace for email related add-ons that can change or replace the standard email functions.
-
The code you need could be something you write into an add-on, or a script.
-
Code. You'd need to hack the code to get rid of this. I'd keep it minimal and change the css to make it invisible rather than try to remove it completely. You could do it with some javascript though, in the announcement banner to alter the css.
-
Natively, no, there's not a lot you can do. You will need add-ons to do this properly. You could try to inject javascript that would link the fields but this is ugly, complex, and prone to breaking in different screens and on upgrade.
-
What exactly are you looking for here? A design approval/review process could probably be modelled in JIRA, but I'm not sure what your review process is.
-
Run a filter to find the issues you are interested in, and save it. You then you have lots of reporting variations, but the two basic routes are: * A dashboard gadget that simply displays them when you visit the dashboard. * A subscription that emails you regularly On your actual search, I can't give you the "correct" JQL…
-
To ge the method you've found to work, you will need to repeat the contents of the import file for every project you have (plus repeat deleting the loading issues) You might be able to do this with the ScriptRunner add-on for Cloud, but I would actually start with some external scripting or coding. Write something on your…
-
You can only add columns that have code behind them that applies to the issues (specifically a template or flag for output and a searcher) The two columns you mention are not issue fields, one is a workflow property and the other a project setting. You'll need code to expose them. The code is actually quite simple, but I…
-
Ok, you'll have to go into quite a bit of debugging now. I'm not sure what's wrong (unless the code you've not shown us here is somehow blanking out the field data you're trying to put into the change), but I'd check the values of variables on each line until you find out where the nulls/empty data is coming from.
-
Yes, good call! That flag can be set when you have an external directory enabled, then if you remove the directory, the flag can remain set, disabling the internal options!
-
I'm afraid you can't yet change the columns in the plan view. Without hacking some code into it.
-
You need to use the class that provides too, ApplicationUser, not User. getUserByName can replace getUser directly