Comments
-
No, the protocol should be fine (you would not have got a anything if it were the protocol). However, I'm not sure it's the network. What you need to try is setting the base url to the address you are going to be running the server on when it goes into production. That could be the ip address, but I'd guess you would…
-
Could you explain "You can't export as soon as there is a next gen Project in the system"? I ask because I've just taken an export of a Cloud system with Next-Gen projects and imported into a server.
-
No, if a person cannot see a page, they can't see any page below it either. You'll need to move the page to somewhere with different restrictions.
-
Your workflow doesn't have a valid transition for what you're trying to do. You'll need to add one to it.
-
Which test case management App is it?
-
That looks like you don't have "attach file" permission in the space.
-
Yep, that's exactly where I was going. You should be able to click the licence pen and paste the purchased key in there, but if you're getting "not for this product", you will need to go back to the my.atlassian.com account that you got the new licence from and get the right key (the one for Software)
-
No, you need to use filters to do this. The only thing in Jira that gets you an issue without using a filter is really the issue view of an issue you've noted down or bookmarked.
-
You'll need to explain what you mean by "sales tunnels" and "navigation tunnel". These are not phrases that apply to Confluence or Lithium generally, so we don't know what you are talking about.
-
Same way you insert images in any Confluence page - drag the files into the page, or paste them, use a macro, and/or click attach in the page options.
-
There's a problem with your network not allowing a full connection to the server from itself.
-
The mention of public key makes me suspect you have Confluence running over SSL (this is a good thing to do, but makes it a little more complex to set up). If that is the case, you will need to put the key in Jira's keystore.
-
No, of course not. It's a service, not a database tool. You can, of course, connect to the database, but you REALLY do not want to. A Jira database is not designed for reporting and reading it directly is absolutely the worst possible way to do any reporting on Jira. Please, forget that idea, it's dreadful.
-
Yes, see https://confluence.atlassian.com/adminjiracloud/configuring-issue-level-security-776636711.html
-
There's no way to do this without going back to a backup. If you don't have one, your only option is to edit the workflow to try to make it the way you want it to work, without looking at what it did before.
-
Start at https://confluence.atlassian.com/cloud/cancellations-873871347.html
-
Yes, that's basic security and access control. It sounds like you want to have some form of automatic login, such that someone logs into your AD once, and their computer keeps a token that can be used to log in to other systems without asking again. This is called "Single Sign On" (SSO), and is not something most systems…
-
No. A page is either visible to a user or it is not. The route by which they see it is irrelevant.
-
Go to Admin -> Application links and add a new application. I'm afraid we can't tell you any more than that, because "it could not work" tells us nothing about the errors or unwanted behaviour is.
-
There's nothing you can do about this, other than get the users to stop saving their passwords in the browser. It's not a Jira behaviour, it's the browsers.
-
What is the error message you get when you try to transition an issue from one status to another?
-
You'll need to look at the docs for whatever browser(s) you are using.
-
Not really, the question is a bit too vague. At this point, it is better that you experiment and learn what the various templates do. You should pick a template that sounds like it is closest to what you're going to be using the new project for.
-
The flag in AD is separate to the flag in Jira. Go to Jira's user management, find the user and turn off the "inactive" flag.
-
You will need to raise this with https://support.atlassian.com/contact
-
The create and view screens (but not edit, as you don't want people to change it later, according to your question). Go to the project settings and look for the "fields" setting area, that will take you to the screens.
-
1. Can we integrate customized pages and workflow to JIRA? Yes 2. How can we delete certain cases in JIRA? Click delete (assumes you have granted "delete" permission to the user, and is strongly NOT recommended because delete really does mean delete - the issues are gone, completely, there's no way to get them back without…
-
As stated many times above, no. It's gone, removed from Cloud. Your only option for the old navigation is to migrate off Cloud on to a Server install.
-
Start with the help/support links that should have been written up on the site
-
Stick with 9.4 - it is tested and supported. The docs do say you can try the 9.6 driver but warn that it may not work. See https://confluence.atlassian.com/adminjiraserver079/supported-platforms-950288096.html