Comments
-
If it's your system, then you are the admin, and you should be able to deal with them. If you're not the admin, then you need to speak to your admins to find out why they're allowing other accesses like this. Either way, if you want our help (as people who are end users), you'll need to explain the probelm in more detail.…
-
Not you, me. I converted it to an answer because it was a metric-shed-load more right than mine and deserved the "right" flag! Glad the hint got you headed in the right direction despite being completely wrong, I'm very impressed by that leap!
-
Sorry, had JIRA on the brain. Yes, Bandana for Confluence (same advice for doing it while Confluence is offline though)
-
With SQL (while JIRA is down), and from memory, the base url is in one of the first 40-50 records in "propertyentry" and you can just splat a new one in there.
-
Ok, that's ruled out the Jira config on a project/notification side, and a problem with your email client. I'd have a look in the Jira email queues to see if there is anything suspicious in there, and similarly, the Jira log to see if there's anything obviously wrong. I think you've covered all the stuff that's in the…
-
Have you changed your profile settings? e.g. email address, or, more importantly, the "email me on my changes" flag?
-
I'm afraid that's mostly up to your mail server. Jira will be trying to delete the email, but if it fails, it can't really have any way to deal with whatever the cause of the failed deletion is, so it just picks up the mail again, and repeats the process. The short answer here is that you need to debug the mail server to…
-
Well, you are looking in the right place - the log fiile should tell you what is happening (it may not be running out of memeory, but running into another problem) What are you seeing in the log file? Around startup would be nice, but the main item of interest is whatit sasy as ut showns own....
-
I'd be surprised if the installers put Jira and Confluence in the same Tomcat - that's explicitly stated as a bad idea on Atlassian's website! You're absolutely right that they should be separate, and the BIN installers should create completely separate installations (including the Tomcats). As long as they are installed…
-
That could be part of it, that file should also be owned by the jira user.
-
Yes, but you need to physically check this. Make sure the directories it's trying to access are all owned by the Jira user, and have full r/w for that user and so-on
-
Start with a look at the application log file - there are probably warnings or errors in there.
-
Definitely use REST for that. A "server side" command has zero advantages, as you need to use either a scrape via the ui (ugly and slower), a direct database read (often painful to construct and you don't want to have to issue it or maintain it) or a REST call. JIRA has *no* command line options, it's a service built to…
-
JQL is not JIRA SQL. It has a lot in common with SQL, but it is not SQL, it's Jira Query Language. SQL returns selections of data, JQL gives you a list of pointers to issues and nothing else.Anyway, Rahul's question is valid - why are you doing this? Not the how, but why? What can't you do in JIRA that you think you want…
-
If this is returning no tables, then you're looking in the wrong place - you've pointed it at an empty hsql database.
-
You need to find the database.log file - look in your plugin directory for target/jira/home
-
Difficult to say without the screenshot, but the "next" button is generally greyed out when the installer doesn't understand or can't work with the information you've provided previously. (E.g. you've given it an invalid path or it can't connect to the database you've told it to use, etc)
-
No, you need to upgrade Jira in order to use that version of Greenhopper.
-
And the rest of the command?
-
You'll need to show us the rest of what you're doing. Your content looks fine, but a bad request is more likely to be caused by how you are posting, or that you're posting to an end point that does not exist.
-
Check the collaborators section on https://confluence.atlassian.com/servicedeskcloud/setting-up-service-desk-users-732528877.html
-
Yes, that's correct. A JIRA Core user is not a Service Desk Agent, so they can't be assigned SD requests. It's the Agents who deal with issues in a Service Desk project. You can involve non-agents as participants though, and if it leads to tasks for developers/Core users, use the "create linked issue" option to create…
-
Ah, ok. Well, you don't. That email address is for sending emails out, and it is usually connected to a handler so that you get comments when people reply to them. If you want more incoming email addresses, you need to set them up on your mail server, and then connect JIRA to that server to process them.
-
You need to explain that a bit more. What's a "mine site"?
-
Create a new custom field (type = select list, with options p1 to p5) and then add it to the greenhopper card configuration.
-
No idea - you haven't told us where it's happening, what you are doing when it happens, or what application it is (the confluence-questions label is almost certainly misleading, unless you've got an addon that connects questions with the application causing the error) From memory, it's usually a git fault, with size of…
-
Jira doesn't have nested groups. You can put people in many groups though.
-
You need to do two things 1) Stop using Jira-users in your permission schemes. Jira-users should be used to say "this person can log in", not "this person can see project X". Separate your users into groups, put all of them in jira-users, but do not use it anywhere other than "can log in" 2) Enable reporter only flag -…
-
You already said that.
-
I'm afraid not - the permissions in JIRA are not (yet) that flexible and granular. Managing sprints does kind of necessitate the ability to manage versions too, and in most cases, someone who manages sprints is generally the scrum master and/or project lead, so it makes sense to tie it to project admin (at least until we…