Comments
-
No, because when you can't see a page, you can't see parts of it. There are some apps on the marketplace that allow you to bypass your permissions and security, but I can't recommend them as they compromise the permissions.
-
If you change the base-url, then the links to the attachments will change to be based on the base-url, if you are looking at the proper attachment links - those generated by Confluence in macros and in the attachment displays inline and in the files list pages. If you've been embedding the links in text, then Confluence…
-
The only way to do it is with SQL (so not on Cloud), and it is strongly recommended that you do not do it.
-
Nothing - the import will have indexed the data already.
-
No technical maximum, but you will find that eventually the exports begin to fail. This is why Atlassian recommend using the database backup for medium and large Confluence systems.
-
Export from one Confluence, import into the target.
-
You have to reduce the size of data by removing things from the export (i.e. housekeep and reduce your Confluence before exporting)
-
You're still asking it to work with a large number of results and it needs to build, hold and work through a huge list. I'd suggest you look at simplifying what you're doing to a sane range of pages.
-
The issue type screen scheme selected for the project determines what set of screens are used for each issue type. Create a new issue type screen scheme and set the project to use it. For different selections in the same field, you will need to create different "contexts" for the field from Admin -> Custom fields - each…
-
If your base url is set correctly, then Jira will be directing people to that. So if something is still saying "localhost", it must be something in JANDI, not Jira.
-
See https://confluence.atlassian.com/doc/migrating-confluence-between-servers-184150.html
-
To become an admin on your Cloud system, you need to ask the site or Jira administrators to add you to the groups that have administration permissions.
-
Returning 10,000 pages is a lot of work, it's going to take time. I'd suggest not doing that, and using the system as it is intended to be used instead (i.e. why are you trying to get so many pages? That volume is useless to an end user, so you must be trying to do something other than provide pages to users which is…
-
It will struggle - even a Pi 3 does not have the resources to run a Jira install fast enough for anything other than single-user testing.
-
>my role is admin Admin roles give you admin rights. Not project rights. Please check the project permissions (admins can always see the config of a project), and check that you are included in the "browse project" rule somehow.
-
Log into the server, go find the <jira install>/conf/server.xml and undo the changes you have made to it that broke it. Then use the standard service start routine to restart the service.
-
If a user "is not in the project", then they cannot see the issue, and hence will not get any emails. You will need to ensure that the user can see the issue, either by being "in the project" or by making the project anonymously accessible. This is basic security.
-
Stop looking at the database, it is not designed for any form of reporting, and unless you understand how to work out the complex queries you need to build your questions, you are wasting your time. Your 1240 is nonsense and useless to you because you don't know what you are looking at. 497 is the number of people who can…
-
For each different set of fields you want, create a different issue type and give them each their own field contexts (and probably screen schemes)
-
It is not a "plugin", it is part of Confluence. Please read the doc to find out how to use it.
-
<sigh> Are you asking about importing these files or editing them?
-
Install, yes. Run it, yes. Run it at a useful speed - well, generally no. The PI has plenty of IO speed, a decent processor (assuming at least a Pi 2, although you can actually run it on a Pi 1), but the memory is going to fail you. My caveat on that is that I tried no memory tuning beyond the basics of giving the OS and…
-
You will need to rewrite all the code that reads and writes lengths of time in Jira's core code.
-
That means what it says - the server is trying to reach the email server, and it's timing out. You'll need to read the full error message, and correct either the connection settings, or fix the network path from the server to email service.
-
Absolutely - the data from 6.4 can't be imported into Cloud at all. Last time I did a migration 7.11 to Cloud failed as well - you really should upgrade your 6.4 to 7.13.
-
The "pretty" date/time display is written to show whole numbers, not fractions of them. If it were to do fractions, it would have to be told what the rules were on when to split - would you display 3.5 days, 3.25 days, 3.0.666 day? Or 7 half-days? etc
-
That's something determined by the type of field - probably best to check the Xray docs and maybe ask them.
-
issue.getStatus() will return the current status.
-
You don't need to worry too much about shutting down Synchrony this way. Shutdown Confluence and if Synchrony continues to run, kill it with the operating system procedure for stopping something.
-
A "handshake error" usually means there is something wrong with the SSL certificates you are using. My guess would be that Bitbucket is on SSL and you have not imported the certificates into your Jira system correctly. Have a look through…