Comments
-
You defintely should raise this with Atlassian OnDemand support.
-
Again, did you change ALL the formats? There are four settings in the admin screens and you need to be consistent with them.
-
Did you change ALL the formats for it in the general settings?
-
The error message is a shade cryptic to a non-computer geek, but what it's saying is that the file you've downloaded is not the file the process is expecting and it can't work with it because it's damaged. Try downloading it again and re-running the new copy.
-
Sounds like the installer is trying to do something it's not allowed to do, or is possibly corrupt. Try reading the log file it mentions, check the system events for errors, and re-downloading the installer.
-
There's not enough context for this question. What are you putting in the file, where, and why?
-
You can build any workflow you want in Cloud, just the import isn't functional. Have a look at the workflow description and you should be able to recreate it manually.
-
Cloud allows some customisations, but nothing that would allow a user to move JIRA into a state where the support team would be unhappy to support the changes - this means no code changes to the core, a limited set of addons available and some of the more advanced configuration functions are locked down.You *can* customise…
-
It depends on what you mean by "customise reports". Jira has some built into it and they can be quite flexible on their configuration. But if they don't meet your needs, then you're stuck on OnDemand because you can't add new plugins to provide new reports or change the existing ones outside the parameters they already…
-
Yes, that's the "dummy user account" approach - the weakness is that it's easy to forget when no-one is the assignee.
-
Mentions are very helpful in getting people involved. But remember that the idea of multiple assignees does not work.
-
I'm not sure I understand the question, so I apologise if this seems like completely the wrong answer... You need to start from the position that no-one can see any issues in Jira by default. Then you can set up rules that say "allow person to see project if..." and use things like "if they are in role X in the project" or…
-
It's not explicit here at a glance, so I'll say it clearly: You can NOT use a group in the assignee field. End of story, there's no workarounds, hacks, tweaks. The assignee is a *single* *user*. Nothing else. The usual workaround is exactly what you've done - have a "group assignee" field. But this is totally separate from…
-
Ok, so you're using a field as a way to keep a group informed about an issue. That has nothing to do with the assignee field, so I'm not sure what the question is, or what is not working here?
-
I don't understand what is not working. You say: >1. created a custom field group assignee >2. add notification scheme to change assignee but not working. >means not changing assignee (Then you've pasted a chunk of the document I pointed you to, but I've no idea why) Point 1 is fine, but point 2 and 3 make no sense.…
-
You can't do it. Jira expects assignees to be a single user account. There was a feature request for this, but Atlassian have closed it with "will not fix". See https://confluence.atlassian.com/display/JIRA/How+do+I+assign+issues+to+multiple+usersfor workarounds
-
I'm afraid it is what it says it is - you are using queries that are too large to be handled.
-
Depends on how you are doing user authentication. Internal? Crowd? LDAP?
-
It's not. In any version. The assignee field is, by definition, a field that holds one single user account. Groups can't go in there because the field holds users. Not groups. You are trying to do "assign to group", which was discussed recently at https://answers.atlassian.com/questions/248664/assign-issue-to-group-in-jira
-
To add to this, there is a good reason - sub-tasks are of little or no use in planning. You can't rank them outside their parent issue (because it's logically nonsense), so there's no point in putting them in there. You can't actually do anything with them even if they were in planning.
-
I'm not sure there's an answerable question here. Project and defect management in JIRA are what they say they are - you can use JIRA to track those things. Then there's a collection of words with no context - I can't tell you anything other than they're things related to issue tracking. And for the last line, start at…
-
You'll need to read the documentation for the mail server you are using. I'd look for the word "whitelist" in it - a whitelist means "only accept mail from people on this list" (And usually can be set up with rules like "must be from domain X")
-
That's not quite clear. Exchange is not going to send the email anywhere. Jira picks up incoming email from a mailbox that Exchange provides for it to read. What you want to do is tell exchange to dump any email that doesn't match your domain before it puts it into the mailbox for Jira to pick up.
-
Filtering email is far more efficient if done by your mail server - most support simple black/whitelists - if you're on a decent mailserver, frankly, it's one line to say "only accept mail from domains X, Y or Z". Rather than have to process it there, then pass it to Jira and have to write something for Jira to do the…
-
Your system is unable to connect to the database. Connection refused means the database is refusing to talk to the application because your settings are wrong.
-
I don't think it's the database type at fault here - you get that error when it can't connect to the database server at all.
-
There isn't a concept of "current/active" version, but you can query for "earliest unreleased version" which is, in theory, the same thing in most cases. Should be the version you are currently working on. Try fixVersion = earliestUnreleasedVersion(ABC) where ABC is a project you want to check.
-
I'm afraid you need a plugin for that - the worklogs are attached to issues, not people.
-
Duplicate of https://answers.atlassian.com/questions/11967400
-
Read the worklogs on the issue. I suspect that's not what you need, but you are not being specific about it, so we can only give you very generalised vague answers