C.Faysal {CFcon} Community Champion

Hi liza. I never used GH simplified flows but i assume they're editable too

Hi all. What happens if you clear the "fix version"?I believe GH uses this one for released issues. If you're able to see the issue in the rapidboard after clearing the value you may need to add this as a postfunction in your "reopen" transition as well

oh sorry for not understanding....i tried in the latest release...that is 6.1.3.1 but what makes me wonder... I see Sprint in the dropdown. But when I give a value like sprint = "Sprint 1" it says no issues found. you said you can add "Sprint" you get no results when you use the sprint id instead of name? like i already…

to find out just try it in the navigator...

oh i missed asking for your GH version... conrad is right.. In Greenhopper v.6.0.4 it is not possible to search for Sprint names in JQL. so if you use latest release this standard jql will work for you

no need to install this plugin for this JQL. but it extends the search function with IssueFunction:

hi umesh. sprint = "Sprint 1" is not correct. i see this is using some IDs instead. so in that example "Sprint 8" has ID 20 jql Sprint = 20

try clearing jiras plugin cache and restart the instance afterwards see what Joe posted here: https://answers.atlassian.com/questions/151453/jira-4-4-5-jira-startup-failed-plugins-did-not-start?page=1#151455

hi. can you completely uninstall it from the UPM and upload the 6.2.2 jar afterwards? you also may check for orphaned files in jira_home example: ls /var/atlassian/application-data/jira/plugins/installed-plugins/ |grep green

can you check if the new icons are accessible ? ls -la <jira>/images/icons/ the all should be readable if you don't see i.e. -rw-r--r-- 1 root root 531 Jan 14 20:24 atlassian-jira/images/icons/issuetypes/task.png you may need to chmod the files (or the images directory -R) to use 644 permissions chmod -R 644…

not exactly what went wrong here but after setting back up to not include attachments it worked for me..at least until i built a cold standby system setup

i understand you point... is the user differing between manual and cron triggered backups?

backup path is as shown above /var/atlassian/application-data/confluence/backups no modifications werde made. right now i just unticked "backup attachments" and manually ran the backup process. it was able to finish and placed the finally created .zip file in backups. but automatically triggered backups wont end up in the…

permissions are set fine.. i can see in ${confluence-home}/temp that the backup process is creating the dumps there. but it won't end up in ${confluence-home}/backups like it did before. all paths are fine. user confluence who runs the app owns entire ${confluence-home}/ and relevant directories in ${confluence-install}/…

wich browser is that? have you tried any alternatives?

do you really have a jira user called "user name" or "User" trying to send an email to "user@domain.com" ??

yep take a lool at https://confluence.atlassian.com/display/JIRA/Jelly+Escalation

Two solutions. 1. like preston says you will need to add in/outbound transitions to your workflow2. use greenhopper simplified workflow

Behaviours plugin lets you hide fields and also modify exclusions. You may give it a try

i guess so. i remember seeing some customfield configuration in the admin area of JEMH. i suggest you take a look at it by yourself reading/searching the documentation. https://thepluginpeople.atlassian.net/wiki/display/JEMH/JEMH+Home

hi robert. i think the built in mail handler is not offering this feature to assign the issue thats been created by mail to a specific person. we use the JEMH plugin. it has an option called "Addressee Handlgin" where you can select a value like "firstCCisAssignee. so the email that is first in CC will be the assignee in…

hmm how was confluence 4.3.2 installed? i can't believe that the selfinstaller came with tomcat 7. even confluence 5.0 is on 6.0.35

hi igor. please have a look at https://answers.atlassian.com/questions/140838/when-new-confluence-user-sign-up-and-logged-in-is-said-not-permitted also this https://answers.atlassian.com/questions/65843/unable-to-login-to-internal-directory-user do you maybe mixed sth up? i assume you meant Jira (latest ?) is on Tomcat 7…

ok. what about this KB article? https://confluence.atlassian.com/display/CONF34/Delegate+user+management+to+use+JIRA+logins i know it is for earlier release of confluence but there may be some similar settings to make in your installation. sorry i never did this in our installations. we use crowd from the beginning so i…

i see. is there a trusted communication set up between both? i.e. this https://confluence.atlassian.com/display/DOC/Setting+Up+Trusted+Communication+between+JIRA+and+Confluence

Hi Damien, i am missing a name like "Crowd" i.e. to provide (what i think your goal is) some SSO feature. telling confluence to use jiras user directory won't enable single-sign-on between both applications. that's where Atlassian Crowd is comming in pretty smooth. this will allow (after some few configuration) accessing…

oh ok now i got you. i guess you talkin bout loggin in to your desktop using your AD creds (like you on a Domain or such) you wanna be logged into crowd/jira/confluence directly right? you mean sth like this? https://answers.atlassian.com/questions/78997/automatic-jira-login-using-ad-user

so only problem you're facing is if you try to access jira and enter youre AD crendentials you're not automatically logged into confluence ? means SSO not workin correnctly right? what if you login directly into CROWD...then change the URL to reach JIRA or/and Confluence...will be be logged in there or do you have to login…

my configuration that works looks like this: Crowd using a connector type directory for checking with the AD. not a delegated type (due to performance reasons) the apps jira & confluence using this directory with a single group per each (created locally in crowd) confluence-users and jira-user other group memberships will…

Hi, is your crowd already using an AD connector? did you set the SSO Domain?