Comments
-
That suggests that you are not giving it a username and password. How are you specifying this in curl?
-
That system is protected by a user name and password, you'll either need to provide them (encoded properly in the curl/wget call) or perform a two step process where you log in once, get a session token, and then provide that in the second "get pdf" call
-
From your description, it sounds like there are two separate systems here, so you'll have to have two separate longs. Nothing to stop you using the same credentials, but the systems are separate.
-
No, it's not possible to set it in the JDBC driver - MS-SQL doesn't support it being set other than in the internal options, so the JDBC driver can't do anything about it.
-
https://confluence.atlassian.com/crowd/overview-of-sso-179445277.html probably
-
Confluence is not a document management system, it is a wiki. The best option is to import the document as a page, or set of pages, and use Confluence as it's designed.
-
Might want to report that as a bug with Atlassian (we're end users, like you, not support or the developers)
-
Ah, ok, sounds like you need to get them to do some tuning of the application and server settings!
-
If your server is overloaded, you should be seeing clues in the logs - "lucene" related errors, memory stuff and so-on are good indicators. Start with them :-)
-
It's not quite that. The Resolution field has no technical link with the status of an issue. We humans make a logical link, but if you dig through the Jira code and behaviour, you won't actually find one. The resolution field is similar to most of the other "single select" lists in Jira. There's a list of possible options,…
-
Oh. You need to remove that option from the list of resolutions. It does not fully explain all of the problem you've had here, but it certainly explains part of it. You got two columns because you have "unresolved" and the system "unresolved" which means "no resolution set". That explains the second column, but not the…
-
Odd looking one that. You definitely don't have a resolution of "unresolved"?
-
It does sound like indexing may be an issue, but just changing the filter should not fix a broken index, only issue updates will do that. It's more likely that your original filter was behaving oddly. Difficult to say why, without the details.
-
Not a clue. You can't even begin to guess a sizing based on users - they're a tiny fraction of your data and mostly irrelevant when it comes to data size. Your data size is mostly determined by (number of issues * complexity * activity). To do even a basic estimate, you'll have to explain your setup and usage in quite a…
-
That's not what a backlog is for, so you don't really.
-
Onkar has just updated the answer with what I was about to say!
-
Where are you trying to "get" it? REST, plugin, javascript, something else?
-
No, you do not have any access to the database on Cloud. You could try raising this with Atlassian support to see if they would do it for you as a one-off, but I don't think they will.
-
Sounds like you've checked the basics, so there's a whole set of stuff I could start telling you to look at next, but it's easier to point you at https://confluence.atlassian.com/display/JIRAKB/Notifications+Troubleshooting and see if anything on there jumps out at you!
-
Ah, I see. Well, the basics would be some form of unique login id (username), and password authentication. JIRA will then take email, display name, and group memberships if you need it to. There are some add-ons for some directories which allow more information to be drawn out of the directory for display and other uses…
-
No. What would be the point of having an external directory that doesn't actually provide users? I'm a bit lost on what you're looking for here.
-
If you're talking about the certificate stuff, it's the opposite. Certificates are handled by a discrete system that doesn't know (or care) about other systems. It hands them out, and publishes revocation lists. Other systems such as JIRA are set up in a way that simply blocks access to anyone without a certificate (and…
-
Not quite. JIRA bases its accounts on the certificates, there's no external links. Group management is done in JIRA for JIRA. You are absolutely right about the need for an add-on - it contains a replacement authenticator as well.
-
Yup. JIRA was not hooked up to a directory (like it is with LDAP and the others). Imagine it more like having a swipe-card (certificate) to your office (JIRA). Present the card and it goes "Ah, you can come in"
-
All of them, I've seen JIRA hooked up to all sorts of user directories. I've even seen it use a non-directory method, where certificates were handed out. Of course, most organisations have some form of LDAP (that includes AD, same basic idea).
-
Yes, that's a good way of doing the "scrape" effectively.
-
You can't do this. If you need to restrict view of something to a subset of people, then there is an absolute logical requirement that you can identify that subset of people to differentiate them from the wider audience. Without that information, all you can do is say "everyone can see it" or "no-one can see it", because…
-
Start at https://confluence.atlassian.com/cloudkb/changing-the-cloud-instance-url-address-or-migrating-to-a-new-cloud-instance-691011835.html
-
Have you ticked the "map" flag next to the summary? You must not do that (it's only valid for data that is going into select type fields - i.e. not text, numbers or dates)
-
The best path is probably * Upgrade the 6.2.2 to 6.4.6 * Copy the config you need from the upgraded 6.2.2 into the 6.4.6 * Export the upgraded 6.2.2, then use project import to pull the issues you need into 6.4.6 There are some utilities on the marketplace that can help you with point 2