Comments
-
What does the application logs say? They'll have more detail about the specific error. Do you have another tool that tries to connect using a jdbc connection? What connection strings are you using?
-
No, the bulk edit is exactly what it says - it performs the same edit on each issue selected. It's simply not dynamic like that. What you CAN do though: Set up the workflow on the issues so that it has a transition like "copy fix" (you can hide it from normal users with a condition like "only admins" if you want). Use a…
-
1. No, you just add them. See https://confluence.atlassian.com/display/JIRACLOUD/Project+Management2. No, you will need to contact Atlassian support as I said3. run filters for "issue overdue" and use filter subscriptions to email people about them
-
* You need to add versions and components via project admin before they will appear on issues and reports. (Roadmap is version based too) * Yes, there's a global advanced setting you can change to get absolute dates at all times. I'm not sure you can change it on Cloud - it's certainly a support request with Atlassian…
-
There aren't any absurd ideas here. To change the emails, you need to hack the templates, and you can't do that on OnDemand. the other option might be to intercept outgoing mails and reprocess them (i.e. mail server gets email from Jira, reads the subject for the issue ID, uses REST to pull the information from Jira, and…
-
Some places I've worked hide the entire space until it's basically ready, others use space restrictions. A couple use closed spaces with limited acces, and then move the pages when they're ready - often their own personal spaces. Depends on if you need a monolithic, mostly static space to go out, or you can drip-feed the…
-
No, it can't be stopped without stopping and restarting confluence.
-
Read the log file to find out why they are stopping, and fix that.
-
Check the permission scheme - you need to have "Create issue" permission or the project won't appear.
-
Depends on your setup. Tempo doesn't actually care if you have Service Desk or not. You will need a licence for Tempo for each separate installation of JIRA. If you have one JIRA on it's own, that's one licence. If you have a JIRA running in one department, and a JIRA Service Desk running in a second, you need two Tempo…
-
You need to use one of the Atlassian accounts that is used to maintain your instance of JIRA, not your Cloud/OnDemand account for logging into it.
-
I don't see that on the 6.1 I'm looking at, it shows the currently selected setting above the list of conditions. I'd raise the issue with Atlassian.
-
Look to the right hand side of the list of conditions for a two-pronged fork - when you hover over it, you should see "add grouped condition". That lets you do the old A and (B or C) thing.
-
No. Screens are done by issue-type (within a project), not by user. The user can have some effect on what's on offer - e.g. if they can't modify reporter or assignee, those fields are surpressed on edit screens. But the view screen shows all the available data to all users. You need the "field security" or "behaviours"…
-
The validator method is the better way to do it anyway, as it can't be bypassed. You should be aware that your company needs to move off IE7 as well - it's obsolete, insecure and unsupported by an increasing number of applications (including the Atlassian suite)
-
You need some code to do this. To do it properly, you'll need to find or write a "validator" that you can add to your workflow - see https://confluence.atlassian.com/display/JIRA/Configuring+Workflow#ConfiguringWorkflow-Applyingvalidatorstotransitions - I'd recommend a look at the "Jira scripting plugin" because it can…
-
They're part of JIRA Core, not Software. Make sure the fields are on the edit screen and try editing the issue - the fields will appear and you will be able to select options for them (assuming you have "edit issue" rights in the project)
-
Crystal reports is a reporting tool itself. If you want to use it, I'd strongly recommend a read-only user is used to read the database, and unless your installation is quite small, only running it against a replicated copy of your database (because it's quite easy for your users to create complex and often useless reports…
-
JIRA permissions are not that granular - you can either configure the board or you cannot. With a bit of messing around with the system-addons I managed to disable the link by disabling modules in Agile, so I'd check that all modules in the Agile plugin are activated. If they are, then the next place to look is probably…
-
Er, removing them from the edit screen does prevent in-line edit. And, bulk edit in some ways.
-
As an admin, check the permissions on the project - sounds like you have got "Create issue", but not "Edit issue"
-
Hmm. Ok, can you check who has "browse users" in your global permissions? If it's just "administrators", could you *temporarily* add a group to it to see if a user in that group can now use the fields?
-
Could you have a look at what type of fields these are in the list of custom fields? And check over the configuration you have set for them in there too?
-
Check your field configurations and make sure the ranking field(s) are enabled. Then go into the project, Greenhopper admin, and then optimise/repair the field.
-
Disagree all you want, but you're wrong. There's been three more questions today alone proving that the "don't send email on my changes" flag is NOT well understood by people. Please don't misunderstand - we totally agree that this is the right behaviour. It's intuitive and sensible to us. I'm not saying the flag is wrong,…
-
Er, no, you're completely missing the point. The test email tests the connection, not your schemes. Let me rephrase it. If you do NOT know that the system is hiding emails to you that have been triggered by your issue changes, then how do you test your notification scheme is doing what it should be? Look at the questions…
-
Then how do you test notifications on a new system (when you don't know that the system is hiding your own emails)? It's immensely counter-intuitive - just look through the questions here - there's hundreds of "why aren't I getting emails?" answered by "you've turned off emails to yourself". People don't know about it, and…
-
You can set it in the default user preferences. Off the shelf, it's counter-intuitive - people testing a new installation will complain that they don't understand why they aren't getting email, but it is VERY useful to turn it off by default once your administrators know about it and can explain.
-
Ah, so you followed the instructions above , as they're the same as the tutorial.
-
That suggests you've removed the role of user from your system, so you may have to use a different one. What do you see when you click edit?