Comments
-
The right to log in is a global permission setting. By default, it's the group "jira users". Your user is not in a group that has the right in the global permissions You need to either add "jira-developers" into the permission (side effect - ALL new users will be put in the group automatically) or add your user into "jira…
-
Check your "notification scheme" for the project(s). I suspect you'll find "add comment" and/or "edit comment" are not set up to be sent to "watchers"
-
Although the evaluation stuff might try to install on a desktop, you can install it on anything, it doesn't matter what type of machine it is. As long as the target runs Java and allows you to put a web application server and the application on it. Heck, if you want a real challenge, you can get it to work on a mobile…
-
Yep, so create has all the fields, and view does not.
-
It sounds like your admins have put fields on the "create issue" screen, but not added them to the "view issue" screen.
-
From memory, the SOAP interface never had link functionality added to it. It's also deprecated and you should move to using REST as soon as possible (SOAP dissappears completely in Jira 7). That does have some stuff about issue links too - see https://docs.atlassian.com/jira/REST/latest/
-
What do you mean by "see users"? A user in Jira can either see all users or none of them, there's no in-between. That makes me suspect you're trying to do something like assign them issues in a project which you have not put them in as possible assignees. I guess my question is "where are you looking, that you expect to…
-
Check that your users have application access to JIRA Software - the access model has changed and you now need to be granted access to each application as well as JIRA https://confluence.atlassian.com/cloud/manage-application-access-744721629.html
-
Please, do not conflate field configurations and screens. They are totally independent artefacts (so, no, you can't associate a field configuration with a screen). It's better to not even talk about them together, as people get confused. If you want something mandatory on create, but able to be blanked out later, you need…
-
There's a lot to be found, I don't think any new admin is able to find it all straight away! (I certainly couldn't when I started with it, and Jira was a lot more simple in version 2) It's quite likely your documentation is trying to cover the scenario where you don't want a field to be mandatory ALL the time. Jira doesn't…
-
No, you don't need the JSU to do this. Jira has, as Joe says, mandatory field options built into it. Go into the field configuration scheme for the project, find the one you are using for the current issue type and you'll find there's a list of all the fields. There ARE mandatory/optional flags against almost all of the…
-
You'll need to read logs to work that one out, but you can't do that on Cloud. Raise this with Cloud Support, so they can take a look and get it fixed for you - https://support.atlassian.com
-
Those both sound more like validators than conditions, but you can do them both. Off the shelf, "make sure a role has a user assigned" is easy - you can just use "user is in role x". That guarantees that role X has at least one user in it. Making assignee mandatory is definitely better done as a validator (and there's one…
-
Go to admin -> issues -> workflow. Click the add workflow button.
-
You'll need to contact the owners of that website. We can't help you with that.
-
Oh, this downgrade again, I thought you'd finished that ages ago.There is no easy route to do this. You're going to need to read each issue in Jira or Page in confluence for their attachments, getting the version you want (all of them?) then extracting the physical file name.
-
That's correct. Confluence renames the attachments to something it can handle because you can't have two files with the same name in the directory and it needs to version the copies. It also dodges previous problems with unusual characters in file names, non-standard character sets and so on. I think the question I'd need…
-
I don't have an answer for that other than "write something that extracts data from Jira and only displays the bits you want them to see" Jira simply doesn't do hiding of stuff like that. You can either see an issue, or you can't. Even the plugins that let you hide fields won't help you here because they'll still let you…
-
You can only see data in Jira without logging in if the project the data is in allows anonymous access. Look at the permission scheme(s) for the project(s) you want to publicise, and look at the "Browse" permission. Add a new group to it - you will find "anyone" on the group list. Be warned though, it really does mean…
-
Have you read the requirements doc for 3.3?
-
That implies it's trying to upgrade on start up. Is your empty system the same version as the source? Also, are you using a supported version of Java for this?
-
That suggests that there is something bad in the config in your home directory. Try this next: * Go back to your clean empty and working system * Stop it * Go to the home directory and change just the database config, so that instead of looking at your clean database, it's looking at the one with your data in it (the file…
-
I don't know what could be doing that - your installation is broken, but I don't know what you've actually done to install it, or even what you're installing. Check the prerequisties for the version you are installing first though.
-
3.3 may be a little different, it's been a while since I used 3. But I think it's the same basic idea. I would get Confluence running empty first - that way you know it's working on the new server.
-
The standard process, pretty much from Confluence 4.0 is at https://confluence.atlassian.com/doc/migrating-confluence-between-servers-184150.html If you've followed that guide and still have errors, we'll need to know what they are if you want help.
-
When you say "Confluence didn't", did you check Confluence directly? Can you try checking the internal url Confluence is on without the proxy to see if it's actually running? If it's running, then we need to look at the Apache settings. If it's not running, or running with errors, then we need to fix that, and a good…
-
It requires code to significantly re-arrange the display on the view screen, so no, you can't do this. JIRA's view moves the "system" fields into a panel, pulls out dates and user-related fields into their own panels and then places the rest in another "custom field" panel. You can order the fields that end up in the…
-
You can't do it without coding in the gadget to restrict things, and frankly, why bother? As Ubisoft says, use the boards, filters and dashboards with the right security and it really doesn't matter what gadgets a user can see - the actual issue data is hidden from them
-
It's not available on OnDemand, that's why you can't find it. There aren't many other options, probably the best you can do is use the "share this issue" link at the top right of the issue view (next to export), but that won't fix your "not a Jira user" problem
-
One shared outgoing email can't possibly work, because you don't know what customer is raising what with you. You need to be able to identify the users in some way, and an account (even a simple customer account that is created automatically and they don't have to log into if they don't want) is the cleanest way to do this.