Comments
-
Many times. Start at https://confluence.atlassian.com/doc/proxy-and-https-setup-for-confluence-950286281.html and let us know if you get stuck
-
If the server is working for some people, but not others, you can be sure the server is not the problem. Because it is working for some people. It might be something networking related on the server, but Confluence doesn't have anything that would arbitrarily block people (even black lists wouldn't give you this error). So…
-
A label will work too, but you always need to edit the filter to include it. For example, set the board filter to Project = Pets or labels in (Cat, Dog, Bunny, T-Rex) And that will give you all issues in "Pets" plus any issue in any other project with one of the four animals as a label.
-
No, most of us do what you suggest - really sparse notification schemes. Jira 8 (Server, not Cloud) is going to have a load of notification improvements in it, which I think will go to Data Centre too, but I don't think they're going to go to Cloud, so you won't be wasting your time with "disable most". No Atlassian has…
-
That is entirely up to your users and processes you are supporting in Jira. You will want a new project when you want to track a set of tasks separately outside an existing project. Consider most importantly the differences in the way you want to track (different issue types, fields, sets of users, workflow) and also think…
-
Confluence won't do that - a refused connection means the network is not allowing it (it usually means confluence is down or not functioning, but if other people can get to it, that is not the case) I'm afraid you'll need to do full network debugging - check what is being dropped or refused when the failing machines are…
-
Connection refused happens when * The service is not running * The service is running, but has failed * A proxy is not connecting (you hit the proxy, the proxy goes to Confluence) * There's something blocking it on your network (unlikely, as this usually gives you a different error) In cases 2 and 3, there will be an error…
-
My guess is that you're on Server, which doesn't have agility projects (only Cloud has them)
-
It's all covered in those docs.
-
Go to "manage applications" to see who has access to each application (it's done by group)
-
See https://www.atlassian.com/software/jira/pricing?tab=self-managed
-
No, Jira does not support a layer below sub-tasks. The Structure add-on can emulate it.
-
This is a 7 year old problem that was fixed years ago, so I'm not sure why you're looking here. However, you should read your log file to see what the underlying error is - that should give you more relevant error messages to help you find the cause.
-
The "best practice" for this issue type is whatever you need it to be. Jira has "issue type schemes" which determine what issue types are available in each project, so you can have projects (and hence teams) with different uses of different types. The value of it is not something we can tell you. There's probably a good…
-
Hmm, it's a bit more difficult if the target system doesn't have a url based external API. If it doesn't accept REST/url based calls, then yes, you probably are looking more at using scripts to access it via whatever remote API it does have. (Webhooks are really just "poke url")
-
I thought so. Epics don't appear because you don't plan then directly - you don't need them in the backlog, they're containers for your stories. They'll appear in the Epics tab though. Subtasks don't appear in the backlog because they're pointless noise in there. They are planned as part of a story, and can only be ranked…
-
One or a combination of: * Plan it properly - do it when your users don't mind the down time * Do it in pieces - export the spaces you need one or several at a time and import them * Use a high-availability system - Confluence data centre
-
There is no API in a random download of part of a system, so that's nonsense. Could you explain what you are trying to do? Not "create project/issue using something" but what you are trying to achieve? What does the end-user get out of this?
-
An end-of-life Jira will continue to work as before, but if anything does go wrong, you won't be supported on it. There are no guarantees of it working (but if it did before, there is no reason to expect it to stop working just because it's EOL)
-
So, can you take a look at one of the issues that you expect should be in the backlog? What is different between that and one issue that does appear? I suspect it's going to be the issue type, but I can't be sure.
-
Ok, so see https://docs.atlassian.com/software/jira/docs/api/REST/7.6.1/ - that will show you the authentication and possible calls you can make.
-
No document tells you to take a database dump of a different version and dump it into a another one. Either export the data and import it into a clean empty 6.13, or create a copy of the 5.5 install and use the installers to upgrade it.
-
I'm not sure that link says much about this. As Alexey already said, Next-gen projects don't (yet) have categories. So you can't set one.
-
This is a place for end users of Atlassian software. While you might be running (or trying to run) Atlassian software on this AWS system, we're not Amazon experts and most of us can't help you with fixing the underlying OS under your Atlassian stuff. I would recommend asking in an AWS forum.
-
That's not going to be a drop-down then, if it's a single entry and different for each issue. That needs to be a text field. You need to decide how you want that populated. Either users can enter it (use a text or short text field) in the UI and/or over REST, or you should calculate it (use a scripted field from one of the…
-
Um, you have working code, so I'm not sure what you're looking for now?
-
Where are you seeing the 14 issues? In the backlog, or on the board during a sprint?
-
@ is being used for "mention", and you have a user who's login is "todo". It feels like an arguable bug - some people will want mentions, but some of your users may have keyword-like logins which will mess it up if mentions are enabled. I'm not sure which way to jump (but to fix this one case while there's no solution, I'd…
-
Scrum is Epic -> Story -> (sub)task. Jira is unlikely to change away from that, as that structure has been fundamental almost since it was first written.
-
Yes, sorry, I went to bed before getting your comment. That file absolutely should be text, not binary (I'm not saying it's a lot easier to read than binary, as it is usually dense blocks of java error messages). Worrying that the install filled the disk, I think you're right to roll back, it sounds like something went…