Comments
-
You don't - this would be an upgrade process, not an import. You'll want to take your 6.4.11 export, import it into a temporary 6.4.11 installation, upgrade that to 7, then export it again
-
Bother. I'm not sure then. ... actually, one other idea. Could you visit Administration -> Global permissions? (On later versions, that'll be Admin -> Users -> Global permissions). Look for who has "browse users" permission. Make sure you have it and retry the assign.
-
Hmm. Then that should work. I have a slight doubt about the "anyone" working though - I think because it's a concept rather than a physical list of people, it might not actually be being parsed. Could you try adding the group jira-users, or a role that other people are in, as well as "anyone"
-
Assign permissions = can assign issue to someone Assignee permissions = can be assigned an issue (by anyone with the permission above) Two separate things in the permission schemes - check those first and get back to us if your roles are in the second one!
-
Yes, I never got very far into it - my comments here are based on trying to do much the same. If you know exactly what Atlassian have tweaked to get standalone in it's current shape, it wouldn't be too hard, but I don't. Grabbing a WAR is far more simple than the investigations to work that out!
-
And the missing libraries? If you're deploying WAR on a clean Tomcat, you need to add libraries. If you've got an existing Tomcat and you overwrite it with a new one, you need to check them for updates. And merge the config files. If you're going to overwrite the Tomcat and go to all the effort of merging, you might as…
-
What about the supporting libraries? It's ok moving the web-app itself, but the Tomcat installation is now missing quite a lot of stuff, and a quick "diff" found around 30 files in the Tomcat install that would need checking for merge...
-
I really don't think you've thought this through properly. Have you compared every single file yet? Worked out exactly what you need to change? Checked for the upgrades and changes in every supporting library? The EAR/WAR version, built off-the-shelf is more difficult to implement and maintain. But it's a lot easier than…
-
Ugh, this is one of the main reasons I avoid using standalone. It's a bit of a pig to upgrade the Tomcat underneath it. In theory, you should be able to take a standard tomcat of the current version, unpack it, work your way through all the files that it contains so that you know what is in there. Then compare it to all…
-
If the contact details are not on the plugin description, check the marketplace entries for the one you're interested in.
-
What does it say on the plugin's contact details? (We still don't know which plugin you're asking about - I know of 3 that do UML stuff)
-
Which UML add on, and have you asked the authors, rather than the community (who don't know what the author's plans are)?
-
The model is quite simple, I'm not sure where the questions are coming from. Ok, there's some complexity around application access does, but... A user who has access counts towards your licence. That's it really.
-
Not quite, that's an answer for an older version and things have changed. You still need to create licenced accounts.
-
You can use user fields in the notification scheme, no need to mess with workflows
-
Correct, they'd all need a licence. Might be easier to simply have fields though - one for each user. You can then put whomever you like in that field on an issue-by-issue basis, no dummy accounts needed.
-
Correct. The main point for "virtual users" is not licencing though, it's to do things without being real people. Ideally, you wouldn't do that at all - all actions should be attributable to users. Atlassian have improved the handling of user accounts and basically disabled your ability to have unlicenced activity…
-
It hasn't changed - you need to create actual user accounts and use them as if they were real users, but it doesn't matter if you set their email addresses to distribution lists, their names to things like "Art Outsourcers" and you never actually log in as them. The bit that has changed a little - dummy users need to be…
-
Yes - https://developer.atlassian.com/display/JIRADEV/Customizing+Text But no, because you're using OnDemand and you can't do that in there.
-
Oh, the admin menu, right. You need to be an administrator. If the cog isn't there, you have no admin rights, as described in the paragraph above it.
-
What settings button?
-
Ok, have you tried clicking "versions" on the plugin page? That gives you compatibility and support information for each version.
-
Nor us. What addons or systems are you talking about here?
-
Service Desk is an application that runs inside JIRA. Whilst it does a lot of clever things, it's not something that imposes massive loads on JIRA (which will then, in turn demand hardware resources). The guide at https://confluence.atlassian.com/adminjiraserver071/jira-applications-installation-requirements-802592164.html…
-
I think you've misunderstood restrictions. Let's say you have a space that says "Confluence users can view the space, and Group my-users can add pages". That limits the people who can add/edit pages to my-users, although all your logged-in users can see the whole space. A restriction then, well, restricts who can do what…
-
We can't see your support request, so you'll need to explain this in more detail.
-
Your code should have retrieved a result set from the SQL query. Add that to the "map" that gets fed into the .vm when the users land on the page. We can't really be more specific than that - where the map is populated, and by what, depends on what your plugin is providing and how you've coded it. For example, a custom…
-
Ah, so you've caused it by "using Firefox" and it's browser specific. I couldn't tell that from the original question.As the solution seems to be "change the CORS headers", I think you want to raise this with Atlassian Cloud support at https://support.atlassian.com
-
What have you done to cause this problem? This is not happening on the Cloud site I was looking at a minute ago, so it must be something different in your configuration.
-
Ok, you're going to need to read the full atlassian log to work that one out. One of your fields is broken, but it's impossible to tell which from just the header error. Go find the first line of that error in your log, then work down from there - it should tell you more about the error, hopefully including a reference to…