Comments
-
You're missing a ".driver." after jdbc
-
Sounds like an odd way to conform to an audit to me. You'd normally test it before promoting to production, and record that. Having historical access to data that might be affected doesn't tell you anything. Plus, "figuring out which fields in which issues needs to be checked" is not a proper test. You should be checking…
-
You could code something to add and remove people from groups, but that really does sound like a horrible hack.
-
Ok, you are on Cloud. Cloud is currently undergoing some structural changes to user accounts (and other stuff) which need parts of it to be static while things are moved around. You will need to get hold of https://support.atlassian.com to ask them when you'll be able to change email addresses.
-
No. An issue is an issue, it doesn't care about the version of JIRA or plugins etc. You could put in a hideous kludge - add fields to contain the data and write a bit of code to store it. A better option would be to log all your upgrades properly, store the dates somewhere safe, and then you can compare the issue created…
-
No, the email goes to the group. They're in the group. Groups are not related to issues.
-
Download the version of JIRA (or JIRA Software, or JIRA Service Desk) that you want. Run the installation Decide if you want to do https in Tomcat (not recommended) or use a proxying web-server to do it for you (strongly recommended), and follow the guide for that. For the install…
-
No, hang on, that's confused. There are three basic installations you can do * Server * Cloud * Data Centre You run Server and Data Centre installations on your own hardware. Cloud is run for you by Atlassian. It is NOT Data Centre, but that is irrelevant to you because you're not running the hardware for it. So, you now…
-
You'll need to remove them from the group(s) getting the subscription.
-
Ok, you're making an incorrect, but very human, assumption about logic here. If I were to ask you a question with a "yes or no" answer (such as "are you left handed?"), how many possible answers are there? Most people will look at the "yes or no" and tell you "two", but they're wrong. There are three: Yes, No, and "not an…
-
Ah, it's Cloud. You'll need to raise this with support, as it sounds like something is broken. Alex has given you exactly the right steps to work out what is broken, but that's not something you can do on Cloud, it's up to the system admins. i.e. Atlassian. Raise it with https://support.atlassian.com
-
No. When you're using Cloud, you are on the version Atlassian currently supports, adn they will update it on their schedule.
-
Same answer - your own email handler could parse emails of any format.
-
Yes, read the "work log" tab on the issue. Or grab it over REST. I think there's a much broader question behind the word "get", but you will need to explain it before we can start to answer it.
-
As many as you need.
-
Yes and no. The technical answer to your question is: Go to admin -> profiling and logging, and you'll find a flag to enable SQL logging. It'll be dumped out to a log file But you have helpfully told us what you're actually looking for too. JQL rarely, if ever, runs SQL. It's too slow. JQL runs searches against the index,…
-
Duplicate - https://community.atlassian.com/t5/Confluence-questions/Add-a-custom-api-wiki-to-knowledge-base/qaq-p/600179
-
Have you added the field to the card layout?
-
Use a simple if: def cFieldValue = issue.getCustomFieldValue(cField) if (cFieldValue) { def a = cFieldValue.toString() def x = a.indexOf('[') def y = a.indexOf(']') def newSummary = a[x+1..y-1] + " - " + issue.summary; issue.summary = newSummary; }
-
Your administrators can shut down and delete accounts.
-
I agree with you on the JSU, especially as it's 12 years old. Atlassian should have bought it outright by now and included it in JIRA.
-
What user directory are you using?
-
I'm afraid they're global defaults. JIRA expects project admins to get their new project and set up the users they need. The global defaults are just there for a basic default.
-
Ack, sorry, that's because I was in an older JIRA mode (upgrading someone, again) By admin, I mean "log in as an admin and hit the administrator's cog at the top right". It'll give you a menu with at least six options, one of which is "system" - hit that. Now, to the left, look for "Project roles" in the "security"…
-
Ah, yes, the problem is "a few years old". JIRA 7.something has more functions. Try fixversion in versionMatch("regex")
-
Yes, the request type is part of the request, not the issue.
-
"Create shared configuration" is not a "copy". It's telling the new project to use the same configuration objects as the old project. If, for example, you look at the "workflow scheme" for the projects, you'll see they both use "Workflow scheme A". If you make a change to that workflow scheme, both projects are affected.…
-
Ah, ok. The message is being generated in the depths of the Scala code which is compiled into Service Desk then. You'd need to pull that out and re-write it (not easy)
-
Yes, because I'm now a bit confused on what the problem is. If only your administrators have admin rights, and developers and jira-software-users have the right access to boards, I'm not sure where the issue is now!
-
I've not tried it yet, as I've not had a need too, but does https://confluence.atlassian.com/servicedeskcloud/managing-service-desk-notifications-732528936.html help?