Comments
-
Cloud, not OnDemand. There's a data centre in the Republic of Ireland. It's in beta, with a number of clients actively using it, and I'd expect to see an announcement that its coming out of beta soon.
-
Natively, nothing, and technically, it can't anyway. It doesn't "know" that more than one person is editing a file on another machine. There are some add-ons in the marketplace that implement locking, so you can flag an attachment as under edit by another user and prevent people using them, but there is no way to prevent…
-
Well, the correct answer is that your DMS is broken as it should not have {} in its urls. They're explicitly listed as "unsafe" and not to be used in correct urls. You can escape them of course, and that will make Confluence accept it as a url - replace { with %7B and } with %7D
-
In theory, yes. But you will still need to reconfigure the target project to accept the data, whatever method you use. In real life, it's going to take you weeks, if not months, to work out exactly what SQL to run to reconfigure your target project correctly, perform all the pre-move data integrity checks, and then move…
-
Well, pages are visible be default, it's not "can see page because I can see parent". It's the restrictions that cascade down. If you restrict a page, then all its children inherit that restriction. You can add more restrictions in the child pages if you want.
-
The type of plugin was to ask whether it's a Server or Connect add-on, as they're structured very differently. As you're working with velocity, that strongly suggests it's an add-on for Server. Your attempt to include the field like that is simply not going to work. A jspa page is a generated page that is built on-the-fly…
-
Ok, that's a good reason for it, but JIRA doesn't think that way, it just fails all validation without order, because in most cases, it doesn't matter. You could remove all the validators and re-add them in field order, but there is a better solution. Write your own validation script to replace the set of canned ones…
-
It's just not been coded that way. Atlassian never got enough people to ask for anything more configurable than "dump everything into a word doc"
-
You have not copied your new licence key from your my.atlassian account and applied it to your Confluence server.
-
The status category doesn't matter, it's purely based on the the issues being in the right hand column.
-
Create a transition from RD BOSS 1 to DBA. Then use your script in a condition on the transition to say "if RD BOSS level > 4". Return false if it fails, then no-one below level 5 will see the transition.
-
Ah, you've added the log. That implies that either Tomcat is already running, or it is crashing hard during startup, or you've got a networking problem. The hard crash is most likely, you'll need to look at catalina.out to diagnose it
-
What does the log say? Look at the ones in <confluence home>/logs and the <confluence install>/log/catalina.out
-
For hipchat, disable the hipchat add-on in Admin -> manage add-ons. Timetracking will appear on an issue as soon as you have an estimate or someone has logged work, you don't need to do anything The bitbucket panel will appear when you've got a linked repository to create the branch in. But your user must also be a…
-
You need a database management tool (I think you typed your comment while I was adding a missing bit to my answer) For mysql, there are loads of options. The basic one is the mysql command line tool of course - it's generally installed by default on the server, but you can load it up on any client and connect to the…
-
Look in cwd_user for the last login date. You can use any database management tool you like to read the database, as long as it supports the database you've chosen for JIRA. I tend to use the command line tools, because I rarely look at the raw database. Remember to only read your database, never write to it with SQL.
-
Your JSON looks ok, so I suspect that either project TP does not exist or the user you are logging in with does not have permission to create issues in it.
-
Your description is a multi-user-picker field, so I'm not sure what you are looking at code for. Could you explain more?
-
This is one for https://support.atlassian.com/contact - you need to talk to Atlassian about this, the community of end users can't really help you.
-
Ack, sorry, that was for JIRA 6-. For 7, it's the groups named in the "application access" section.
-
Is the desired project lead a user who is active and able to see the project?
-
Not without hacking the core code that takes you there.
-
Ok, that's healthy. Next, can you go to "application access" and make sure your account is included as someone with JSD access?
-
Notifications, not permissions! Some of what you're seeing makes sense. The issue assigned event should feed into a notification that goes out to Watchers, the assignee (old and new - this is one event that is a bit different to others), and the reporter. However, all of those are JIRA (Core) system-roles. Not Service Desk…
-
That's not what Agile boards are for. You need to be able to point at an issue and know what status it is in, representing where it is in its lifecycle. Having it in two columns is nonesense because it makes the status and columns useless, as above. But, that is boards. Your desire to represent a set of issues based on…
-
Ok, it's not installed properly then. Check what you have under "manage applications"
-
Go to "create project" - do you get a set of project types in a "service desk" section?
-
You don't. If they own the dashboard, they can edit it. If they don't own a dashboard, it's not theires, so they can;t.
-
We would not be advising you to do it if it could not be done. The best mthod is not complex - set up an empty postgres sdatabase, export your data to xml, point JIRA at the empty database, then import the xml via the UI.
-
Hmm. Last time I did that, I was able to just set the remote server in the log4j properties file and it worked fine. But that was a while ago (years)