Comments
-
You won't get an answer to this beyond "when it's ready". See https://answers.atlassian.com/questions/2892/release-date-of-confluence-4 for the last time something similar was asked - it applies to all of Atlassian's software.
-
> The folder seems to includes the two directories you mentioned; one for the application and one for that's data No, it does NOT. There's no data directory in there. >I set the JIRA HOME directory to the path of "atlassian-jira-5.2.7-standalone" using JIRA Configuration Tool That's what you did wrong. You've pointed the…
-
This is actually quite simple and it's telling you what you've got wrong. Jira needs two directories (although you can use more if you need to) - one for the application and one for it's data. You must NOT put one of them inside the other. What you've done is name a data directory and then put the application inside it.…
-
One of your users who is also getting the "create issue" email has an autoresponder on. Have a look at the headers of those emails - they should tell you who it is so you can tell them to stop, or remove their email address.
-
Not unless your Ecas system can generate the logins. It sounds like you need a form of SSO for that with JIRA. To do that, you'll need to find/write something for Crowd to become the user directory for Ecas, or find one of the 3rd party SSO solutions that can handle Atlassian with others.
-
The user directory is handled inside the application, you need to log in as an admin to see it.Start at https://confluence.atlassian.com/bitbucketserver/lockout-recovery-process-776640158.html
-
The error message you've got is saying that Stash cannot connect to the user directory you have set up for it. At a glance, it looked like it was an embedded Crowd (that's the name for "An Atlassian application using a cut-down copy of Crowd internally to handle users) in JIRA, but re-reading the log, it might not be. Now…
-
The log file says that Bitbucket cannot even *reach* the JIRA server to read the users. You need to fix that - it's either- A config error in Bitbucket- Your network not allowing the connection, - JIRA isn't running- JIRA is not allowing access to Bitbucket (I'm not sure you can do that with embedded Crowd)
-
> The remote authentication server is not available That answers the question - Bitbucket Server cannot reach the JIRA server to read the user details.
-
If you think it's related to groups, then you need to compare the Stash (Well Bitbucket now) settings for groups with the changes you have made.
-
Ahh, excellent :-)
-
You seem to be missing the point here. The upgrade documentation you were pointed to earlier is what you need to follow. 4.4.5 to 5.2.11 should be quite straightforward. But you've ignored what was pointed out earlier (messing around with entityengine and the fact you're losing data are indicators that you've not…
-
The short answer here is simple - you should not need to mess around with entityengine.xml >However, after the upgrade process, the database data entities from JIRA 4.4.5 are not transferred to 5.2.11, resulting in zero JIRA project That's the bit that worries me here. If you've followed the instructions, then ALL your…
-
You could raise it with Atlassian Support to see if they would install a language package for you, but I suspect they won't do it as a one-off.
-
You don't. System administration is limited to Atlassian support, you won't ever get access to it. Your account should have "JIRA Administration", at the highest level.
-
There is a misleading disconnect between JIRA and JIRA Software. JIRA has a convenient panel that displays the estimates and worklogs from sub-tasks on a parent issue, and provides a couple of functions for summing them up in searches and so-on. JIRA Software does not expect you to estimate at the sub-task level and does…
-
Check the space permissions - it probably says "let confluence-users have access", and you are adding your people into that group to allow them to log in.
-
Not really, Jira doesn't do field level security - field access is determined by the project configuration, not who is looking at the system. Exceptions are the assignee, reporter, due date and versions fields, which are partially controlled by permissions.
-
Always worth trying a restart first :-)
-
If a restart doesn't help, you might want to try clearing the cache - https://confluence.atlassian.com/display/CONFKB/How+to+Clear+Confluence+Plugins+Cache
-
I don't really understand what the question is. The structure of the data has changed because it needs to for whatever reason. I understand that this has broken a query you are running, but I do not see why it's a problem, because you don't explain what you are trying to get out of the query. "What do I have to do to have…
-
Correct. However, it is perfectly fine to copy and rename one of these "simplified" workflows to use as the basis of your customised one. They are normal workflows, it's just that if you do edit them as an admin, and leave the users with the option of "simplified", you may run into problems.
-
Workflows labelled like that are usually generated by JIRA Software, when certain types of projects are created, or an administrator clicks the "simplify workflow" button on a board. Workflows that are simplified like this should not be edited manually by administrators, as any edits could be destroyed (and some won't work…
-
Most scrum masters I know *really* like the ability to create what they need when they need it.
-
REmove their right to administrate the project?
-
No. You can have "project" admins as well as the three you mention, but that's done in the permission scheme and just allows project admins to maintain users in roles, versions and components in the projects where they have admin rights. See https://jira.atlassian.com/browse/JRA-3156
-
There isn't - the look and feel customisation in Jira is more primitive and doesn't support css etc. You can add javascript to the banner and field descriptions (which isn't ideal), but for many changes, you're looking at tweaking core code.
-
Er, it's your system - you should know where you put it!
-
The JIRA server can't find a running Stash on the url you have given it. Check the urls carefully, the network routes and that the server is running.
-
You've said "through the updated multiple custom field values" again, without explaining it, and that's the main problem with your question. Your "clone issues and inherit data" is now clear (which wasn't explained before), but you really need to explain the "updated". Updated in what?