Comments
-
Definitely need better pictures - I can't see that problem at all.
-
Er, no, you've uploaded small pictures. Zooming makes the pixels bigger, not clearer. You need to upload better pictures. It would be really useful to get them with the column headers included as well. I can't see anything moving to the right in the pictures. The layout varies between versions, but the columns line up so I…
-
I'm afraid I can't really make out what the problem is here, as the pictures are too small. The columns look right to me and it looks like the layout has changed slightly, but it's still consistent with the rest of the grid? Could you give a bit more detail?
-
Yep - see https://confluence.atlassian.com/adminjiraserver070/advanced-workflow-configuration-749383189.html for more detail
-
Hmm, could you have run into https://jira.atlassian.com/browse/JRA-17004 ?
-
That was the culprit when I last ran into it. I'd also check 1. That the attachments are not too large for your Jira (general settings should tell you what the maximum size is) 2. Your logs - there's likely to be a warning or error telling you why it can't attach the file
-
Does the user sending the email with the attachment have the permission to create attachmnets in the project?
-
Um, I still don't think it makes any sense. Participants is a derived field. To remove yourself from it, remove yourself from the rule that catches you. Or, come up with a different rule, and code that.
-
No, participants is a "dynamic" field - it works by reading other fields and adding them all together. There's no way to remove someone because the references to them only exist in other fields. You'd need to remove them from those fields to enable the removal. I've seen it rewritten in a couple of places (and I've done it…
-
Issue security is there to hide issues, so I suspect you've set the security to something that stops you seeing them. As an admin, look at the issue security scheme for the project. That will tell you who can see what levels. Make sure your account matches every level. Then look for the issues again.
-
Ah, you've misunderstood the doc, although, having just re-read it, I can see how easy it would be. It's not a case of adding a permission from the list you've given here in the question, it's a parameter for one of the options. "Anyone" is actually inserted into the "Group" option on the list. Select Group, and it will…
-
I suspect there's another question here - about watching a page without actually having an account. That is not possible. A computer needs something to identify a person to send mail to, or log in, or record activity etc. Confluence takes the simple route and requires a user account to attach this information to. The user…
-
The user must be a confluence user. We don't know how your confluence is set up to define user access, but at the very least, they must have "can use confluence"
-
There's some more info about how Jira does permissions, and links at https://answers.atlassian.com/questions/74269/granting-access-to-individual-projects
-
"Dot assign" and "assign to me" are all part of the GUI, so I'm going to guess that you mean "I can't edit the assignee" Have a look at the "edit" screen for that project and issue type. I suspect it does not have the assignee field on it. You can only change fields in the issue view if they are on the edit screen.
-
There isn't an installation log as such, it's mostly the initial attempt to start it. The places to look are in /logs beneath the installation directory you gave it, and /logs beneath the jira-home directory you allocated for it.
-
I can't tell you - I don't know where you put everything when you did the installation. The versions of JIRA are different and will contain slightly different stuff, but I simply can't tell you what you did. If one JIRA is running, start there - its system info should tell you where the install and data directories for…
-
If the services are there, there has to be an install behind them. It's hard to say what might have happened here, you need to go back over the installation and logs to try to find out where things are running. If you can get to both JIRA installs, the system information page will tell ou where they have been installed…
-
That "not recommended" is not an Atlassian thing, it's about resourcing. It doesn't matter that you are running Jira 5.1 and Jira 4.1 on the same machine, you could run more, all on different versions. As long as they're completely independent (different data directories and installations etc). What is NOT recommended is…
-
Boris's answer pretty much covers it. Use REST to extract the data you need, and store it within your app. It will NOT be in any sense a "snapshot" - REST doesn't expose everything (only raw issue data really). If you're serious about a snapshot, then you should simply dump the database, or run the xml export (assuming the…
-
We're not support and we can't get into your instance. I suspect you've broken your groups though. First, go into admin -> global permissions and look at what groups have the right "jira users". You have to be in one of those groups to be able to log in, so make sure your users are in one of the groups.
-
Correct, Cloud does not allow directories other than the internal one and google accounts. I've heard some muttering about allowing LDAP to provide customer lists on Cloud, but I don't know if that has made it onto a roadmap with Atlassian yet.
-
The last time I worked with this addon, I think it was hard-coded, so you had to have the group it mentions. Is the group defined on your system with the correct users?
-
It's group membership - see https://sites.google.com/site/crazycookiecoders/services/jira-plugin
-
I think the groovy runner can do it too. I've not seen a plugin that would solve this one (I do really like the idea though!)
-
That is not how the labels field works - it does not have a pre-set list of options, its suggestions are based on what users have previously added. In other words, you have to have some issues with your desired labels already added before it can start to make any suggestions. The importers only import issues.
-
Run a filter for the two issues, configure the issue navigator to show just "issue id" and "links" You won't get the issue ids, you'll get the actual keys of the issues.
-
No, it has no special rights within JIRA. Anyone in the "JIRA admins" group should see the same things it does
-
You can't get it. JIRA System Administrators permissions are strictly limited to Atlassian Cloud support. You can only get JIRA admin rights, at the same level you're on. What are you trying to do that makes you think you want system admin?
-
It's the permissions for the other projects that those users should NOT be able to see - you've probably got "jira users" in the browse permission for them. (Or possibly "all users"). You need to remove that, and allow access some other way (e.g. create another group of "internal users" and use that instead).