David Toussaint [Communardo] Expert

Ah, so the context defines which template is going to be used in workflow post functions?

Hi Septa, thanks for your support! Exactly that did the trick, safed me a bunch of time. Thanks again :) Cheers, David

Default values are set for both affected Security Schemes. Though one has set "none" as default (whcih is also present in the other one, just not default) and as soon as we switch the project the security scheme gets NOT changed (as "none" is available in both shemes, but onle the default value in one scheme). So that…

Basically it gets applied, just only initially. Though, when the project changes (to a project that has a different devault level) the pre-set security level from the first project will stay and does not change to the default level of the "new" project. Kind of annoying!

Hi Nick, thanks for your answer and sorry for the late reply. While I agree with the idea to just "throw away" steps at all (but we cannot do that obviously) I now have to keep names of status and steps in sync in order to not create more confusion for our admins. Again this brings me back to my initial two questions: 1)…

Is your user allowed to edit issues (i.e. "Edit issues" Permission) in all projects appearing on that board? It sounds like he/she is not. In order to change the just modify the Permission Scheme of the project (or all projects) used by this specific board. See also:…

Hi, I am affected as well. Luckily I only installed it on our development Environment. Regards, David EDIT: I might add the note that this is with JIRA 5.0.3 in my case.

Hi, you need two things for it to work in JIRA: * The global Permission "Browse Users" * The Renderer of the field you are using (e.g. comment field oar any custom filed) needs to be "Wiki-Style Renderer"* set this in the corresponding field configuration That's all that's needed. Also this actualy should work out of the…

should'nt be too far away, there is allready a m11 build publicly available...

Another indication is (in this case) the ond-of support announcement for Tomcat 5.5 which will no longer be supported by JIRA 5.2. On this page it says, JIRA 5.2 is "due towards the end of 2012" whatever that may mean...…

do they have valid email adresses? Could you go to JIRA Admininstartion -> System -> Mail -> Send Email and try to send a mail to that Project role? As your just in that section please do check the email queue and error queue, just in case...

Can all the mentioned users acces the corresponding issue? Unfortunately you are not on JIRA 5, otherwise you could use the JIRA Admin Helper plugin to track down the problem.

Email Templates (two times, HTML and Text) are found in the following dírectory: <JIRA install>\atlassian-jira\WEB-INF\classes\templates\email\ You can simply edit or exchange the files here. Cheers, David

Wow, that's great to know, thank you!

Hi, you should check the following plugin in order to do this: https://marketplace.atlassian.com/plugins/at.celix.jira.plugins.column-order It's not possible out-of-the-box... Hope that helps? Cheers, David

Hi Miki, basicaly for like 90% of all fileds JIRA can not apply different permissions for different users. The 10% left are made up by FixVersion and Due Date for example. In order to enable users to modify those two fields, you need to grant JIRA permissions in your permission scheme to those users (most likely project…

You should go to your field configurations an select a different renderer for that field. My guess ist you are currently using "Wiki Style Renderer" and you should try to use "Default Text Renderer". This should probably do the trick for you...

just pushing this one up, I guess someone is knowing this...

Hi Paulo, thnaks for your answer. while I do understand the basic configuration of application links my question was how to deal with the following setup: JIRA: ActiveDirectory + JIRA Internal directory Confluence: ActiveDirectory + Confluence Internal directory The challenge is that the internal directories or not the…

you're welcome, allways glad to help :)

as pointed out above. I edited the post to highlight possible ways.

Hi Janiv, to find issues from a specific sprint, you have to add one of the following to your JQL query: sprint = ID sprint in (1,3,4) More details are described over here: https://confluence.atlassian.com/display/JIRA/Advanced+Searching#AdvancedSearching-SprintFor this you have to know the ID (not name) of your sprint.In…

Hi Vishnu, you should try the Plugin User Group Picker, it's free and should serve your cause. I tried it a few months ago and it worked well, dooing exactly what you are asking for. Hope that helps? Cheers, David

Hi, Stash EAP ('beta') releases will most likely appear on this page: https://www.atlassian.com/en/software/stash/download-eap Hope that helps? Cheers, David

Hi Andre, I have never heard of such a function in JQL and clearly the documentation only lists searching the text area of comments. There might be some undocuemnted feature though, who knows :) Sorry for that. Cheers, David

Hi Pawan, I suggest that by "cloning a JIRA" you mean cloning a single JIRA issue. If that is not what you'r speaking of, please make it clearer. The most likely cause of creating several issues is that the are having subissues and those subissues are cloned as well. So in order to avoid that you will have to clon issues…

now, why is it bad if the real username is listed? As they can not create issues everyone would know it's been done by email... Anyway, another idea would be to forward the emails. So the user send the mail somae random imap and the mail gets automaticly forwarded to another imap which is where JIRA is listening at.

That's what I guessed. why do you need the reporter to be set to suggestion? There might be another way to achieve what you're looking for.

One way to do this is to prevent the users from accessing the JIRA project. JIRA only acts like you described it if the corresponding JIRA user (i.e. email sender) has the permissions to access the project. So to force JIRA to use "suggestion", you would have to prent all other potential senders to access the project.…

true. though, you could also base the estimation on the number of issues (must be configured in Board configuration).