Comments
-
You are using the wrong url. Your code is irrelevant if you are looking at the wrong url. Remove the .json
-
The example you've found looks wrong to me. Try the same url, but with no .json on the end.
-
Log into my.atlassian.com go to licences -> your licences (which may not appear) -> Sourcetree -> download licence
-
Not really. Confluence does a form of clustering and has done for a while, but it's not for redundancy or fail-over really. See https://confluence.atlassian.com/display/DOC/Confluence+Clustering+Overview Jira. No. End of story. But Atlassian are very much working on it and you can expect something in Summer -…
-
It's not held, it's calculated from the licence.
-
People tend to use Confluence as a knowledge base alongside JIRA, as the integration is quite handy. If you use JIRA Service Desk, there's a lot more power to it as well - your users will be offered self-help Confluence articles as they start to enter questions/requests.
-
I'm afraid it's not directly logged. All you can do is ask the users who have the permission to do it.
-
Think it's stuff in propertystring again, but I prefer to use command line switches See the mail stuff on https://confluence.atlassian.com/display/JIRA/Restoring+Data
-
Normally, I'd yell "don't touch the database", but a colour scheme modification done via SQL during the migration into a non-production system before you start the services is actually going to be fine. (Never adjust a database while an Atlassian product is running, that way lies madness, or rather screaming for backup…
-
I'm afraid it's still the same question - how are you relating groups to issues?It's no good saying "this project has some groups". Although the table implies you're looking for "number of issues by customer and group", you have to define the relationship.To get you part way to that table, and hopefully explain why you…
-
How are you storing the relationship between a group and an issue?
-
Because Cloud is always maintained at the latest version of JIRA that Atlassian consider stable. Rolling and constant upgrades are one of the selling points.
-
Backup -> download will give you an export (you can use it every 48 hours) The import that into your own JIRA installation. However, if you're going to start doing that, I'd recommend looking at moving off OnDemand/Cloud and moving to hosting that will support your other dashboards. Or, if you don't want it in a JIRA…
-
You've almost answered your own question - it is possible to construct a "create issue" url that will pre-fill the project and issuetype automatically. The link you've got is almost what you need - just change the "CreateIssue.jspa" to "CreateIssueDetails.jspa" and lose the &Create=Create bit. That will take you straight…
-
Not internally, but clicking "print to pdf" in the browser works for me.
-
At the end of the trial, your system becomes a production system, which has costs.
-
By "system account" do you mean what you later call "System"? Could there be something else locking or reading the files in there? (The usual advice is to run Confluence as a dedicated, minimally privileged user, but that's a minor point and I don't think it matters here)
-
That "unable to clean" error almost always means you've (accidentally) changed the ownership of part of the installation, either by running it as a different user, or by trying to "be secure". Check ownership and permissions and that you're running Confluence as the user you intend to permanently.
-
Check that issue linking is enabled in Admin -> Issue links Then check the permission scheme for the project to make sure you have permission to create links.
-
That's not strictly true, sorry.
-
JQL can be run in the UI (not SQL) - try "project was XYZ"
-
You'll need an addon to do that (and I don't think there is one in the marketplace). Comments are comments, that's it, off-the-shelf. There's no way to separate comments into separate sections on a group-by-group basis.
-
I'm afraid not. In Jira, maintaining users is restricted to administrators. There are options - you can use external systems to maintain users (Crowd, LDAP and so-on). Another trick might be to enable Jira to create users when they send it email. I've used the script runner plugin to generate users as well. But I'm afraid…
-
Yes, you should have workflow transitions to do this, and it's your users who should use them. Do NOT have a resolution of "open". It will still mean "resolved". You need to use the post-function "update resolution to none".
-
No. You need to tell it to do the transition (and probably set the resolution as part of the transition)
-
See also https://jira.atlassian.com/browse/JRA-3821 for the request to do this properly
-
Issue type schemes are not a way of tagging projects, they're configuration items. Hence, as JQL is for searching for issues, it's not something you can do. You'll need to find/write an add-on to provide a function for it (or possibly a scripted field). Or maybe use project categories better? Although, you could start the…
-
As already pointed out, you need to put the user into rm.group for them to be able to share with it.
-
They need to be in the group to be able to share with it.
-
Plenty, but the question always comes back to "what do you actually want from an 'integration'?"