Comments
-
Auto refresh what? Which screens and on what event?
-
You've called the link type "Clone", the clone process is expecting one called "Cloners"
-
Go to the same place you removed them from and look for "add". You have destroyed the old data though, so you won't get any historic links back.
-
You'd need to find or write a reporting add-on to provide that. The closest you can get off-the-shelf are the "created vs resolved" gadget for the dashboards (which relies on the resolution), and there are other gadgets and reports which work off the workflow status. If you used status properly, or mirrored the extra…
-
It could, if malicious code was added into it, or it enabled a user to embed malicious content in the body of the macro. Only admins can add user macros, so you have to trust your admins not to write macros that do those things.
-
You can't "edit" the type to change between parent and subtask types, the configuration for them is incompatible (one has no parent, the other has it and it is mandatory) Individually, you can use the tools menu on the issue view to convert them - there will be a "convert" option in the menu as long as you have edit rights…
-
Yes, but you should not use them. The Jira database is just a data store and is very very not designed for reporting. It is the worst possible way to do reporting for Jira. If you must do this the wrong way, look at changeitem and changegroup, joined to at lease jiraissue, then you'll need to join it to options to read…
-
It usually means the proxy in front of your server has gone wrong, or is unable to reach the server that should be serving up Jira. Talk to the server admins about the proxy - you'll need to read its logs.
-
If you have let the account lapse, then I'm afraid you have lost all your data on Cloud. Unpaid accounts are completely dropped after a short period (a week I think)
-
The easiest way to do that is to enable and use "Reporter Browse" permission - see https://confluence.atlassian.com/jira064/current-reporter-browse-project-permission-720415972.html (Yes, this is for version 6, but it is valid. The new docs for 7 have lost the page and the search is useless in the new style)
-
They are coded into properties files, not held in the database.
-
I use https://developer.atlassian.com/server/confluence/lucene-boosting-strategy-module/ to weight the search correctly (Atlassian's default is better suited to social media than anything else, which is the one thing no-one uses Confluence for)
-
Without any code or add-ons, you've just described a custom field of type "cascading select list", Try adding one of those to your Jira. The only difference between your description and what they do is location - the pair of fields for a cascading select appear next to each other on one line.
-
To "roll back" to the previous version, you restore the backups you took before you upgraded. Installation directory, database and home directory, in full.
-
Atlassian blocked it to prevent people doing horrible things to their users, like having pages with the same name.
-
There's no "rejection" of a problem, just re-iterating what has already been pointed out. It's "complicated" because it's flexible. Gives us a steep learning curve, but I've never worked out a way it could be simplified, because there is nothing in the system of schemes that you could remove without losing the flexibility.…
-
In all but the most simple cases, you can have "simple" or "flexible". Pick one. Atlassian have gone for "flexible". Jira is complex when you are an admin, yes, but if you don't have this complex/flexible thing, you can't make it work for your users (unless they all do everything in one single standard way you can dictate…
-
If you have Jira Data Centre, then ignore this answer and look up in-place upgrades. Otherwise, an upgrade from Jira 7.3.6 to 7.3.9 is the same process as going to 7.7.0 or above. Download the installer, and point it at your current installation, it will upgrade it. On https://www.atlassian.com/software/jira/download click…
-
The desire to change an issue type is usually indicative of a broken process. It should really be reserved for genuine "clicked the wrong one" or "I completely misunderstood the type names" cases, and hence something you would normally do manually. Two projects is a good solution.
-
Some of them in AO_<somthing> tables, but several different ones, and you may have used scripts from the disk as well.
-
Should be just admin -> addons -> ScriptRunner -> registry
-
Hard to say without knowing what type of "scripts" these are. If they're ScriptRunner scripts though - try the script registry, it lists all but behaviours.
-
Without add-ons or code, no. There's nothing wrong with having different workflows that - where did that "requirement" come from? Workflows can easily share the same status - just because "Bugs" have to go through the extra step of "regression tests" doesn't mean they can't use open, in-progress, ready for uat, uat done,…
-
No. If you don't upgrade now, don't worry. We spend a lot of time here advising people on upgrade routes. If you leave it a while, you will start to get the advice "do not upgrade from 4 to 6". But intermediate versions will remain available, and we'll be advising you to use them! I've just told a client they need to go…
-
I don't think our opinions differ that much. Only really that "implied voting" is what most people expect from a flat voting system like the one that's there. I think we both totally agree this system is inflexible and not really that useful! Have a look through…
-
Absolutely. If you do this in a "scripted field", def A = issue.getCustomFieldValue ( customFieldManager.getCustomFieldObjectByName("A") ) is the basics of getting the content. Repeat for the others, then return (double) (A + B + C + (D/2)) Set the "template" to numeric and the searcher to a number range.
-
No harm in renaming the step to something when you can (yes, Jira will handle the database for you). The step names are independent of status, but it can be a lot easier for admins when they match!
-
@NhajebiYes, I think you should. @Paul Moody [Bauer Information Technology]- I didn't mean to suggest you should remove all of your posts! The spam system picks up repeated similar posts, and the community definitely prefers focussed relevant posts, on the more recent postings. There's not a lot of point telling people…
-
I think you are completely missing my point. An implied vote is the best option given a flat single vote system like this. I raised it, therefore I wanted it. Why should I then have to vote on it? Neither implied or explicit voting works for everyone, definitely. But there's no point in talking about it. They've got a…
-
Running it as a service has some advantages. There's a bit more logging at a system level, but the main one is that you don't have to think about starting it every time the system (re)starts. It will come up automatically on every reboot if configured correctly (and as we all know you have to reboot windows far too…