Comments
-
If you expose the system to the internet, then your users can have whatever access they need - they'll be able to log in and colloborate as though they were in your company. Some people will layer extra access control in front of that, by using a proxy that people have to log in through, but that's a network trick, not a…
-
I kind of understand why it's set up like that - admin rights are totally separate from user rights. Sharing stuff is a user right, and it's correct that users should be in the groups they're going to share with. But yes, it would be nice if admins could bypass their group membership in this case!
-
I suspect you have to be a member of the group you want to share with.
-
None - we can't help you directly, we're end users like you are, and don't have access to your Cloud system You need to visit Atlassian Cloud support, and raise an issue with them - https://support.atlassian.com . They'll prompt you for all the information they need on the account side (which Cloud install it is, who you…
-
I don't think it's illogical really - you've seen @mention work for users, and it makes a lot of sense to imagine that JIRA would support mentioning other issues, and it's a logical assumption that there would be a similar tag to use for those. Not needing any tag is not the intuitive answer when you think about it like…
-
Yes, you don't even need any notation, just using the task key like ABC-123 in text will do it.
-
Not sure what you mean by "reference", but all that happens to the issues is that they get stamped with a version which is then released. A Kanban board (usually) excludes issues in released versions from view, but it is just a view of data - the issues are all there to be searched and used as normal in JIRA (and you can…
-
Never put the resolution on an edit screen, it should only be used on transition screens (and then only on the "close" type transitions). It sounds like you are trying to use the "edit" screen as a transition screen as well - separate them out, have a screen for edit and a screen for resolving/closing issues. Take a look…
-
Not without code. Jira needs to ask for the issue type because it's structural - it determines most of the schemes that the rest of the process will be using. There's no way to restrict users to issue types, so you end up with no option to do this sort of thing. You could try hacking the screen in the core code, or mess…
-
Not via email/comment, but Service Desk is having improvements aimed at better self-service added to it. If you have a Confluence Knowledge Base hooked up to your Service Desk, you get some big benefits: * When users go to the portal, they are offered a search before they go to "create call". This lets them search the…
-
I'm afraid Xander's answer is incomplete. To be able to edit the fix version(s) of an issue, you need to have resolve permissions, as well as permission to get into an edit screen (Edit issue is not the only place you can change fields - it's possible in workflow too) Viewing the fix version is easy though - as long as you…
-
I'm not sure that it is - the thing you need to keep in the footer is "Powered by Atlassian" with the link to Atlassian's site (not the the logo)I can't remember which addon it is - work your way through the system plugins to see it.
-
The "about Jira" in the menu - I can't remember exactly which module it is, but you can turn it off in "plugins". I seem to remember you also lose "online help" and a couple of other things too. As for the footer, it's illegal for you to remove it. You may edit it, as long as you leave in the "powered by atlassian Jira"…
-
I'm afraid none of those are particularly well exposed. Although instinctively, they sound useful, they aren't that useful in themselves. If you're looking for housekeeping, your rules as to what counts as "usage" and "active users" need to be refined, and if you're looking for performance or sizing, you only really need…
-
Have a read of https://confluence.atlassian.com/display/AOD/About+Your+Data to get started with
-
As Be Do has already said, if you allow "anonymous" access, then anyone will be able to read your Confluence. This does not take up any of your license seats. Only logged-in users take up a licence.
-
I think you mean "never estimate subtasks". Estimates should not be done on subtasks because Atlassian haven't coded for any of the seventy three different ways people might want to handle estimates at that level. But, they're very useful for breaking down stories into pieces that are managable, or need to go to different…
-
Please do raise this with support.atlassian.com - that's the best chance of getting a response from Atlassian.
-
Ah, Cloud IS effectively where they test UI change with selected users. I'm afraid you signed up for this when you chose Cloud. It's unlikely you will get a roll-back, but as the message says, report it to support.atlassian.com and add your voice to the noise about it. (Here at Answers, we're end-users like you, not…
-
That's not something an application would normally log, as applications aren't really expected to fail (I know, they do, but when they do, it should trigger an investigation and fix). As Radu implies, some form of external monitoring is appropriate here, and for this, I too would recommend running a simple grep over the…
-
If Jira is running on localhost:8080 but you can't get to it on the same machine on <ip address>:8080, then I'm afraid either your network setup on that machine is broken, or you have not managed to open the port on the firewall. A quick test would be to simply ping the local ip address from the server - if that works,…
-
You, or one of your admins, has added a validator to the workflow transition that requires that field to be changed. You'll need to change the workflow to remove it, or use a different workflow.
-
There's two main log files for a JIRA - the catalina.out is the application server (tomcat) log file, and there's some stuff over at https://tomcat.apache.org/tomcat-7.0-doc/logging.html - again, it's more about general config and changing it, but it's a start on understanding the file. The other one is the…
-
No. That configure fields setting is a personal one for you to choose to ignore fields in that project if you want to. It's nothing to do with the rest of the users or the projects. To configure the projects, log in as an admin and re-configure them the way you're supposed to - see…
-
>to have a global configure fields for all various issue types as a default that is shown in all different JIRA screens I am sorry, but that makes no sense, it mixes up a few concepts within JIRA and I really cannot work out quite what you are trying to do with it. Could you give us a simplified description please? Short…
-
You can't really, but there is a display trick that may help. Probably the least helpful answer ever! If you look at the story in the issue view, there's a time-tracking section which can toggle a view of the estimates and work logged for sub-tasks on and off. But it is just a display, and it causes us problems, as there's…
-
There's no direct cost, but you should budget for your time and resource to do the work. The migration time is mostly down to the size of your data - a few thousand issues will export and import in minutes, but when you're heading for hundreds of thousands of issues, it'll take hours. You should test this before you do it…
-
You have to get a new Cloud system, export the old one and import it into the new one (then let the old one expire) See https://confluence.atlassian.com/cloudkb/changing-the-cloud-instance-url-address-or-migrating-to-a-new-cloud-instance-691011835.html
-
Um, hang on, you've got quite a clear error there - "java.lang.ClassCastException: java.lang.String cannot be cast to com.atlassian.jira.issue.customfields.option.Option" - that is telling you that your code has stored a string in the field, but the field is only capable of handling options. So you need to change your code…
-
This looks very similar to https://answers.atlassian.com/questions/34137/jira-4-4-4-migrated-project-to-new-workflow-but-closed-issues-doesn-t-reopen and I suspect you've got broadly the same problem - you've got a custom field which has code that doesn't work for some reason, but the core of Jira needs that code to work…