Comments
-
Components belong to projects, so when you move an issue from one project to another, the components have to change (usually deleted). It will preserve them if you have the same named components in the target, but you have to make sure they are there before you move. Also, not having defined the project component list is…
-
* I would recommend adding a bit more memory to the server if you can - Service Desk is quite a large addon and has an impact on performance in general. Not a huge amount, but it is noticable * Confluence is fine - the connection and Knowledge Base stuff adds no more than any other space, so you won't notice it.
-
Um, you don't need to. Security levels are based on attributes of a user (group, role, etc) which are exactly the same as the ones you get in permissions. You can simply use the same list of attributes you use in the security level as you use on the "create" permission. For example, if your security level X says "only…
-
Which CRM addon is it?
-
It was a duplicate when I answered, the text was almost identical. The Service Desk mail handler does not have functions to do that
-
Duplicate of https://answers.atlassian.com/questions/43557112
-
I'm not sure what you mean by "JIRA main page", but the easy answer to this question is "because you have not added it". Could you explain what you expect to see on the "JIRA main page"?
-
Ok, it always displays the system field, but custom fields are fair game. Can you check over the settings you've got? Start at the project admin level and look at what "issue type screen scheme" you have on the project. That tells you what "screen scheme" is in use for each issue type. Select the "screen scheme" for the…
-
The view screen rearranges your fields and mostly looks like it ignores your "view screen" settings. It's not, it does read the screen, but it pulls out sets of fields and drops them into different panels - user/groups, dates, time-tracking and the system fields for example. Once it's done all that pulling out, the…
-
This is a standard "use a custom field and give it several contexts" task. Have a look at https://confluence.atlassian.com/display/JIRA/Configuring+a+Custom+Fieldand check out the "context" part which lets you configure fields differently by project/issue-type
-
You can't. Permissions are done at the project level, you'll need to go over each in turn to look at the roles and schemes.
-
I'm afraid you can't. Atlassian built Agile without the ability to move between status in the same column, and although a lot of us have asked for it, they've shut down the feature request to allow it with a "we don't have this on our roadmap" comment, so I don't think it will ever be implemented
-
I think you have misunderstood what events are for.An event is fired as a result of a change to an issue (and a couple of other places, but it's still a change of something). They are fired at the END of the process, and are there for "listeners" to react to. A listener is a background process which has no user interface.…
-
Look at the existing post-functions on the transition - JIRA will add five of them for you automatically (and you can't remove them) One of the standard ones is "fire event", which will probably say "generic event". Edit it, changing it to your "move issue" event.
-
My guess is that you've not tuned it (Assuming it's not whatever is making Cloud slow on your machine). The defaults are good for a demo or small system, but it almost always needs tuning if you're going to use it for slightly larger systems. Remember that there are hundreds of thousands of users NOT experiencing slowness…
-
That's the thing - there is something different between your setup and mine. I've got a bog standard Mac, running Firefox and a fibre connection to the internet. I'm in the middle of the UK, and Cloud works fine. It's not quite as snappy as the JIRA that's running on the desktop next to me, but I can clearly blame that on…
-
Because it's not slow for most of them, and doesn't crash standard browsers? "How do they have so many customers" is an excellent question - if everyone were having the problems you are having, then they would have lost them. Their customers obviously don't have these issues, so the question becomes "what are you doing…
-
Cloud is running fine for me at the moment, so you probably need to do some diagnostic work. Where are you based and is your network slow?
-
Because it's not unusable. I don't have issues with any of the Cloud JIRA systems I've used, barring one, which was down to a really shoddy network connection.Atlassian have recently announced that there are now more active instances of Cloud JIRA running than there are active licences for Server versions, so it really…
-
There are two things here.1. Some users experience massive performance issues with Cloud JIRA, despite having decent network connectivity. Atlassian don't seem to be doing anything to fix this, so those users need to consider hosting it with someone who will fix it (check the partner/expert list) or hosting it themselves…
-
There's all sorts of reasons it could be "slow", but as it's a new installation, it's quite likely that... * You are not giving it enough resources (while leaving enough for the OS to run smoothly too) * You're running it on Windows is always a bit of a pain - most things run better on Unix, I regularly see performance…
-
Do you mean an old Cloud url? If you contact Atlassian support, they will be able to tell you if you can recycle a previous url
-
There isn't one. You can't "harden" JIRA 3.2 it has a number of security issues that are only fixed by upgrading to a supported version.
-
To expand on Renjith's answer (which is completely correct by the way, I'm only piping up because some people sometimes need a bit more guidance) What have you tried so far, what do the errors say, and what documentation have you followed?
-
This is all about networking to be honest. Jira and Confluence are pretty basic web applications when it comes to how they talk to the outside world. You run them on a server, then they listen on that server for connections to <ip address of server>:<port number> Whether your server is reachable from the outside or whether…
-
No. The link won't even show for them if it's a standard internal confluence link (the text will be there, but no underline or link, as it knows they can't see it)
-
Nip over to the space you want to protect and go for the admin settings. Look for the "Permissions" Change the list of people and groups who can "view" the space, removing whatever it is that allows the admin group to see it. If you want to do it at a lower level (pages), then just add a view restriction while editing a…
-
Um. I didn't emphasise or include this fully before: You can not include your admins in the "can use space" and as they browse, they're subject to restrictions placed on pages like any other user, so they won't see it as part of their normal activity. But they will always have the ability to give themselves "can use" and…
-
No. An admin can't do their job without admin rights, and a full admin can always bypass anything you set up in the software, so Atlassian haven't bothered to try to implement anything like that. You can not include your admins in the "can use space" and as they browse, they're subject to restrictions placed on pages like…
-
Yes, you need to share the filters too. It would be nice if JIRA had the option to at least compare the filter access with the dashboard so it can warn you that a dashboard may have one or more broken gadgets for some users.