Comments
-
1. As @nbhushan says, no, it would be a breach of your licence to remove or change the "powered by atlassian" bit, and the link behind it. It must be visible to the user on all pages where a footer appears (i.e. most of them). You can, however, move it around, remove the version and any other links you want, and add…
-
Set the notification scheme to send email to reporter and assignee on the issue created event. The mail handler does nothing differently to a user clicking "create" - the same event goes out to be picked up by the notification scheme.
-
Ah, I was about to say much the same. For a column to appear in the navigator, it must belong to every issue that the filter *might* return. e.g. if you have a field called "fred" that only exists on "Bugs" (by virtue of the "context" settings for the field), then if you run a filter for "bugs and features", you won't get…
-
Hmm. That's odd, it's not what I got last time I looked - I had a "permission denied after create" incident before Christmas, and there were attachments there (the reason it was a problem was that the user lost the attachments and wanted a copy from Jira, where we realised his profile was wrong). Can you read the log file?…
-
You have to be able to see something before you can do anything with it. If you allow "attach" without "browse", then it's a bit like asking someone to play snooker, blindfolded (And not telling them where the table is). You *must* grant browse to issues before the users can attach things or do anything else with it. There…
-
Mmm, it was spectacularly unclear. You've never defined what a "security issue" is for a start. I was assuming you needed to hide them properly from users and had implemented that. Now I understand that you've got an issue type that you don't want to send email for, but your users should still be able to see it in Jira.…
-
Then you need to find out what you have configured that is letting it leak this information and turn it off. If a user cannot see an issue, Jira will not send email to them, unless you've bypassed the security on emails. It's usually a plugin like JETI or a script-runner function to send extra emails or a post-function to…
-
You mention the security level field - Jira will only send email to people who can see an issue, so if you're using security levels, that could stop the emails to people who shouldn't see them. (Unless you've configured something like the JETI plugin which allows you to leak information to users who couldn't normally see…
-
There's quite a lot more to think about than those three questions. Please read through https://confluence.atlassian.com/migration/jira-7 to get started with!
-
The default is 2, but Support will change it if you ask.
-
You'll need to get in touch with Atlassian Cloud support - try https://support.atlassian.comin My account for the project I created disappered before the free trial is over! anyone know how to fix or what could have happened? i updated payment info and all looks good to me but I still cant access my project eventhough the free trial is not ove Comment by Nic Brough -Adaptavist- September 2015
-
Yes and no. If your two issues are in the same project, then converting XYZ-123 to be a sub-task of XYZ-456 will work fine, and it will retain the key of XYZ-123. If you are moving it across projects though, then no, it will need to take on the project key of the new project and get a new number. You'll still be able to…
-
No, and I don't think you'll ever get anything that powerful (script runner I mean, not auto-transitions). The script-runner is very powerful because it lets you use the API directly. Which can be horribly dangerous because it absolutely requires that you understand the basics of the API, at least well enough to know what…
-
To what? Upgrading? Or waiting for the calendar add-on to be updated?
-
Yes, it's safe, but you'll lose the calendar functions.
-
There's no way to force people to enter anything in your wiki, accounts are the only real option.
-
You'll need to get them to register as users, and disable anonymous comments.
-
You have not undone all the changes you made when you changed the port. You need to go back to the configuration you had when you had it working. The "pool not open" message implies you have changed the database connection settings in a way that has broken the pooling database stuff, but we can't tell much more than that…
-
JIRA Agile is an addon for JIRA. It can't run alone, it's using all of JIRA's data as well as the application as a container.
-
It's quite hard to answer this question. Jira is immensely flexible, and can be adapted to handle all sorts of things, so we can't actually say "oh you need to do X, Y and Z". On top of that, it's very fuzzy what SDLC might be. I'm afraid the best answer is actually for you to do more research - look at Agile guidance,…
-
Ah, yes, sorry, that needs answering first. The coffee has worn off here.
-
Ok, the next step is to find out what fields are on the "view" screen for that project/issuetype and find out what scripted fields are on that list. Then look at the scripts behind them.
-
I suspect you have a broken scripted field. - the board tries to display something and the script behind the field is failing. You might want to read the application log to get the full error and see if that gives you more information
-
The last time I looked at Wim's database plugin, it definitely supported cascading select lists. See https://studio.plugins.atlassian.com/wiki/display/JDVP/JIRA+Database+Values+Plugin#JIRADatabaseValuesPlugin-Configuratingcascadingselectcomboboxes
-
I'd agree with that. You should encourage your users to use the front-end. It will help reduce the volume of calls if it's integrated with a knowledge base (because as they start to raise issues, it will point them to self-help), and it'll make them give you the information you need to help them.
-
You've made the field required, the method of raising a call is irrelevant, it should respect the requirement.
-
It's the other way around. You associate a field scheme with a project. (Minor quibble with the question, and probably more about language than the technical points) Log in as an admin, go to the project, look at the config and find the current field scheme. Click on the configure link and select the scheme you want to…
-
It sounds like you're looking at a doc for an old version of Confluence, which may well be valid and retained as historical. But it's not clear because you don't tell us what page it is
-
Could you explain what you mean when you say "issue organiser"?
-
Yes, although do not do it while JIRA is running.