Comments
-
Not necessarily. You just need to make sure that if you use one application server, it is powerful enough to run both at the same time. (Even for a reasonably small system, with few users, I wouldn't try it in less than 6Gb RAM on the server)
-
Correct, with one exception. If you have up to 2,000 developer types then you are ok on Cloud. If you have more, you either need more than one Cloud instance, or to be on Server. But if your 5,000 are mostly "customers" on a Service Desk and not using Jira as full Jira users (so they use a portal to ask for stuff of your…
-
Start at https://confluence.atlassian.com/enterprise/jira-sizing-guide-461504623.html and https://confluence.atlassian.com/doc/server-hardware-requirements-guide-30736403.html And yes, you can use the same db for the stack. You need different database areas of course, but one server with one service is fine.
-
There's nothing you can do on a board level. If they want a neat board, they need a neat workflow behind it. However, yes, I'd have a look at the "resolution" field - it's there for logging "why something was done/cancelled/put off/etc"
-
Does the field have a value when you're trying to display it? Jira will only show custom fields if they have content.
-
The Key for an issue is a key object, and a text field will take objects that are derived from strings. You should be able to do something like issueToChange.setCustomFieldValue(customfield, issueToGetKeyFrom.getKey() )
-
Odd, I'd expect the same from the Jira service. Have a look at the top of the start-jira.sh and start-confluence.sh files - do they have lines like ### BEGIN INIT INFO# Provides: jira# Required-Start: $all# Required-Stop:# Default-Start: 2 3 4 5# Default-Stop:# Short-Description: Jira### END INIT INFO
-
I am afraid you have missed the point of my answer. A security level is not a string. That is why it fails. Your post-function needs to read the string, find the equivalent security level and set that.
-
I've got no interest, but I suspect it's the way it is covered here in the UK more than the competition. I do have one unusually good thing to say though - the 1967 winner is really nice. I used to make tea for Sandie Shaw when she was working with my mother.
-
I don't think the posting above has quite understood the problem, as that still runs straight into the problem that your sprint estimates are broken, and you're failing to meet the "deliver or do not" that scrum is based on.
-
It's very common to do exactly that. To expand on my set up at home - I have one database server, one application server (with Jira and Confluence, so 2 Tomcats) and one web-server/proxy (which I also use for a vpn, but could just as easily be used for LDAP) I tend to lean on…
-
I'm not sure what you mean by "roles", sorry. The installers will default to installing a Jira user, and a Confluence user to run the applications as. The web-server/proxy will use its own user as well, whatever the OS defines for it. But you shouldn't need to think about configuring them. They're OS users who exist to run…
-
The question for me is do you want to run two Confluence systems or just one? If it's two, then you can export the old space(s) and import them on the new one, and then start working on editing the new one. If it's only one, then it might be a bit more painful. You can still export each space you want to copy, but then you…
-
Not quite. At the most simple level, think of each application as having a group of users that "can use application". It's quite common to have a group for Jira users, another for Confluence, and another for Bitbucket, although some people simplify when they have the basic case of "everyone in organisation can use" and…
-
Atlassian's Cloud data centres are in the US and Ireland. There are no others (yet). I'm not sure there are plans for new ones for a while.
-
No. You need to go to the 2,000 user tier. The software only accepts one licence at a time.
-
Multiple Tomcats is fine, as long as you are a little bit careful with them. Different Tomcats for different applications may have different Java requirements. As long as you configure them correctly (e.g. Tomcat 6 runs application 1 under Java 1.6, and Tomcat 8 runs application 2 under Java 1.8). For more recent versions…
-
You said "column" so it looked like an existing field. You'll need to find or write a field that can extract what you need and expose it to the issue navigator if you want to export it that way.
-
I would upgrade the three you have, they're very good at what they do, and mostly at the top of the list of the ones I would tend to recommend. If you do decide to select others, changing the plugin key is NOT going to help you. It will just trash what you do have working. Apps use the keys to store their config and data…
-
I suspect they are "app users" - users created because an App (add-on) needs a user. I would change the permissions to use roles (as they're a lot more flexible). In this case, assuming you have not done much with permissions yet and are close to default, I would * Work out what users you want to be on the assignee list…
-
My understanding is that it's a weighting system. It looks for various patterns in the postings and if it finds one of them, it adds a certain weight to a counter. Once the weight goes over a threshold, it's treated as spam. Code blocks have a bit of weight, but that has been reduced. Code inside the code macro/formatting…
-
There's a lot of reasons a post might be marked spam, the algorithms are not simple, but not spectacularly clever either. Posts with external links or code or random words are the main triggers, but there's also volume of repetetive text or even things like [] in titles instead of using labels. I've had a look and…
-
I guess those users are in the group jira-software-users as well. (Previously, the "any logged in user" would have been allowing them in)
-
What type of field is it?
-
https://confluence.atlassian.com/jira064/migrating-jira-to-another-server-720411862.html is good for all versions of 6.x
-
Treat migration and upgrade as two separate steps (even if you do them together, plan them separately). It does not matter which one you do first. Although if you are changing the operating system to Linux, I would usually recommend moving server first and upgrade later, as that is generally slightly easier. The best…
-
No, I'm afraid there isn't.
-
Start with a look at the permission scheme for the project. There is a rule in there that says "Assignee (who can be assigned an issue)". It's likely to say something like "Role (Users)" The users you don't want to have on the list all match that rule. You need to adjust them, or the rule, so that they do not.
-
This is because of your Comala workflow, it's not configured quite right for your account. This explanation needs to start with how Confluence works, so we can understand what Comala adds to it. In Confluence, you create a page, which becomes immediately available to the users (assuming they have the right permission to…
-
Your admins need to enable it in the add-on section. Be aware it can open security holes.