Comments
-
Ok, that add-on is no longer automatically available to Cloud as it's being rewritten as a Connect add-on. See https://confluence.atlassian.com/jirakb/jira-timesheet-reports-and-gadgets-removal-from-jira-cloud-792504481.html for the details and what you can do to get the functions enabled on Cloud.
-
Which time-sheet reports add-on are you using?
-
Ah, ok, it's not the "queue idle" that's the problem, it's stalled indexing. Start by running through https://confluence.atlassian.com/confkb/confluence-fails-to-process-index-queue-automatically-213524919.html - there's quite a few things on there to check up on I'm afraid, but hopefully one of them is the problem
-
I'm not sure what you're seeing or what the problem is here? Do you actually mean that items are going into the indexing queue, but the queue never deals with them, so the list just gets longer and longer?
-
Eh? There is nothing to "fix" here. "Queue is currently idle" means that it doesn't have anything to do. If you want to give it things to do, create/edit pages.
-
Ok, that's for the main application. I don't believe MS-SQL throws that error, so I suspect you've got something else that is using a connection to a PostGreSQL server somewhere. Do you have any of the "database lookup" custom fields, or any other add-ons that might be trying to read a database?
-
Which one of the two databases are you actually using?
-
Not sure I can elaborate beyond what you've already done! If the projects are all using the same "issue type screen scheme" and "field configuration screen", then they're all going to be seeing the same thing.However, there are a couple of less obvious things to check - assuming you have the two I mention above the same,…
-
Change all project schemes to use the same settings.
-
I'm sorry, but that doesn't help. JIRA is an issue tracker at its heart. It tracks issues already. Could you explain what "track tickets" means to you?
-
Track what in JIRA?
-
A lot of the functions in Jira are provided by plugins. When you install Jira, it includes a whole load of plugins as standard, including many of the reports, the custom field types, views of issues and so-on. Those bundled or "system" plugins are the ones I think of as "Atlassian" because they wrote them, and bundled them…
-
Ok, I'm stuck - there's definitely a problem with select lists and the portlet, but I can't see what it is. I can't replicate it on the 3.13 I've got here, so there's something in your system that is different from standards. Could you list all the non-Atlassian plugins you have installed, there may be something in there,…
-
Hmm. Could you tell us what the name of the field is? It looks like it's struggling with that, or possibly the indexing of it - is there a chance you could try re-indexing the system at some point?
-
Ok, so it looks like select lists. Is it single-select lists, or multi-select, or both? Is it consistent (i.e. always breaks) or does it happen at random What does your log say (you've posted a partial error, which is useful, but a copy of the full output might tell us more)
-
That's a slight improvement. Now the rest - how have you set up the filter, the gadget and the custom field? We're probably most interested in the custom field - what type is it? Does the gadget work if you select a different field but the same filter?
-
That's a bit like telling your mechanic "my car doesn't work", but not bothering to tell him any more - you can't expect him to fix it without any information, like whether it's a blown tyre, low on petrol, driven into a tree... What's the error, what do your logs say and how have you set up the filter, the gadget and the…
-
Hmm. That's not what you've got on the workflow on the issue. Could you check over each transition and see what the label for each one is?
-
I think you might be mixing up transition names and status names. Could you look at the whole workflow (diagram or text) and look at the transitions that say All -> Status - do they have the names you're seeing?
-
No, you can't do this - there are no permissions you can use relating to links.
-
Have you hooked up your Jira to your email server? If that's working, then outgoing emails about accounts should be going out as well. (Seehttp://confluence.atlassian.com/display/JIRA/Configuring+JIRA%27s+SMTP+Mail+Server+to+Send+Notifications - it talks mostly about notifications, but the stuff about the email server is…
-
Arg. This has been explained to you already. Your Atlassian account is for support and bug tracking. It is NOT an OnDemand account. Please read the answers and comments on your previous question. https://answers.atlassian.com/questions/53603/how-to-add-as-a-administrator-in-jira-how-to-add-product-in-jira
-
Ah, hang on, there's an assumption there, and it's not right. You can NOT assign issues to a role (or a group). Only a user. It's trying to assign the issue to the current user. There are functions in a couple of plgins that allow you to assign to the last user who touched the issue from a particular role, but it's still a…
-
Ok, I think there's two things here.First, I've talked about the condition above. The condition stuff is *just* covering "who can do what". It doesn't change the data itself, it really does just say "only a QA person can do this". You should find that if you log in as your developer, they do not have "in review" as a…
-
There's not actually a huge amount to do for this one, but it's not quite clear what you are aiming for. We don't know what your process flow is really, and that's what we need in order to be able to translate it into a workflow. But I can have a go at the principles for you. Let's say your process is broadly New problem…
-
Actually, that really is screaming "two accounts in Jira" (And most likey, with two different email addresses and aliases to land them in the same inbox). Seriously, check the email headers for "to" REALLY carefully (Actually read the physical email address, not the rubbish things like outlook obscure it with) and check…
-
Hmm, that is interesting, that implies 1) A rule on the email client that is duplicating the emails as they come in, based on something like "they have [JIRA] in the subject" 2) You have missed an email distribution list that the user is on The next step is a bit of a faff, but there's a few things to look at. It depends…
-
Ok. If there's no duplication in the Jira list of users, and you're not using email groups/lists, then there's something iffy in his email account. You might need to talk to the email administrators, but I'd check his machine for unusual incoming email rules. With all the fun I've seen with emails, I've yet to see Jira…
-
Is the user in any groups or lists on your email servers that are getting Jira emails?
-
You need to make sure that the issue type screen scheme for each project points to the same screen scheme for the issue type. You also need to check that the field configuration is not hiding fields, and that all the custom fields have a context for both project/issuetype