Peter Van de Voorde Community Champion

Hi Alex, I think you should report this as a bug, because the confluence documentation clearly states that all links to pages should survive a move : https://confluence.atlassian.com/display/DOC/Moving+a+Page#MovingaPage-Movingapagetoadifferentspace Best regards, Peter

I can recreate this behaviour by not specifying the project and/or the specific issue types in the jql of the filter that's being used by the 2 dimensional filter statistics gadget. So just extend the jql of your filter to specify the exact project and 9 issues types, that should help you out. If that doesn't work, please…

Is this customfield available in a global context or not? Does your filter takes the customfield context (issue types, projects) in consideration?

Which system are you talking about? On Demand or Hosted Atlassian tools?

Hi Sonic, Just wondering: what happens if you change the from address of the emails that are being sent? (You can do this in the project administration page just next to the notification scheme). Maybe this specific email address is blocked by some rule or spam checker? Best regards, Peter

Hi Sonic, Does your team mate still receive notifications when you change something? Could it be that something changed in your email server (a new spam filter for example)? Best regards, Peter

Hi Richie, If you want your customers to register themselves you'll need to open up your Jira registration. Otherwise they'll have to be created by the administrators before they can use the Service Desk. Here you'll find some more information about public sign up for JIRA :…

I'm glad you fixed the problem :)

Did you try removing the application links completely and recreating them? Do you get any errors in you JIRA or Confluence log file? Can you use the JIRA Issue macro to create a new issue in JIRA from Confluence, or does this also fail? Best regards, Peter

Hi Tobias, Do you have configured your application link to use trusted communication? https://confluence.atlassian.com/display/DOC/Setting+Up+Trusted+Communication+between+JIRA+and+Confluence Best regards, Peter

Hi Jamie, There is probably a workflow post function on the transition from To do to In Progress that automatically assigns the issue to the user who moves the issue. If you have administrator rights on you instance you should be able to edit the workflow transition and remove this post function. Best regards, Peter

Why don't you just create a transistion between those two stats in your workflow?

Hi Hung Dinh, I just added it to a create screen in my demo workflow and it does not show put so you can't seem to be able to edit it. Best regards, Peter

Hi Hung Dinh, The field the service desk uses is non editable, so you can't edit it. What you've probably done is create another custom field of the type Customer Request Type, but that will not be the one being used by the service desk. Best regards, Peter

Hi Hung Dinh, There is a custom field called Customer Request Type that will indicate which issues are customer requests and which ones are not. Best regards, Peter

Hi Tsougkrianis, We can't help you with this, your best bet is to contact Atlassian support here : https://jira.atlassian.com/browse/AOD Best regards, Peter

Maarten, If the group anyone has Browse Project permission on you project you don't need a Jira user account to see the issues. (They won't be able to edit or comment on them) If your company will not allow a public project for those issues you could create inactive users for the people you want to inform and add them to…

Maarten, You can make a project public to anonymous viewing, so people without a jira account can still view the different issue. Just as the group Anyone to the permission Browse project in your permission scheme. Best regards, Peter

Hi Svante, Some more information can be found here : https://confluence.atlassian.com/display/APPLINKS/Creating+Links+Between+Projects But there is nothing really extra special you can do with the project links (except for the activity stream). Best regards, Peter

Hi Bruce, You could actually expose the entire server structure that is not only supporting your own confluence site but countless others. Sometimes Mommy is right :) If you really need this feature why don't you consider a Confluence you host yourself? Best regards, Peter

Hi Chee-Hong, A lot changed to how sprints are handled in the latests version of Jira Agile (formely Greenhopper). I think you are having a similar problem to the one discussed here : https://jira.atlassian.com/browse/GHS-8168 You could also try the solution that's provided in the comments of that link. I hope it will help…

Hi Which version of Greenhopper are you currently using? Are you creating these sprints for project X and Y in the same board? Can you provide a screenshot of the report screen showing the problem? Best regards, Peter

I instaban those accounts as soon as I see them (which removes all their posts). Everybody with 3000 or more Karma can instaban accounts. Simply click on the name of the spammer and select instaban underneath the cog icon menu to the right. But it's indeed very annoying. Best regards, Peter

Hi James, Are you using multiple projects in the filters behind the board? Do you know which project key seems to be null? Can you find more information in your jira log file ? Best regards, Peter

Hi David, this is probably the problem : Client with address "10.255.152.54" is forbidden from making requests to the application, confluence.type Status reportmessage Client with address "1 0.255.152.54 You'll need to add that ip-address into the application configuration of confluence in crowd. Take a look at the…

Hi Valentin, Couldn't you simply use a piechart based on a filter that only shows Epics and base it on the Moscow value to do this? Best regards, Peter

You'll need to add LDAP as a User Directory to Crowd using the Directory Connector. You can select the option to administer the groups locally.

Hi Korneel, This is certainly possible. I'm currently managing about 70 groups in crowd with users that are authenticated through LDAP. All groups are created and managed in crowd and none in LDAP. Best regards, Peter

Hi Yoann, Can't you just order them by created date and see which one are the oldest and still not solved? Be aware that in Jira Agile, an issue can only be part of one sprint so you'll need to keep the old sprint id's in a custom field if you want to do it like that. Just wondering. Best regards, Peter

Add a label restriction to the filter behind your Kanban board. Or use a sub filter. You can learn how to use filters behind a board in this KB article: https://confluence.atlassian.com/display/AGILE/Configuring+Filters Best regards, Peter