C.Faysal {CFcon} Community Champion

I'll try to find out. For now just import the cert into the keychain of the java that stash uses and see if integration works.

You can add java_home in /etc/environment or in ~/.bash_profile for example. Or in $stash_install/bin/setenv.shTake a look at jiras setenv.sh. I believe you should be able to adapt this java_home variable setting

can you please check if both apps are using the same JAVA binary? i.e. ps axf|grep jiraps axf|grep stash by default Jira uses its own JRE i think stash choses the JAVA from your hosts environment in that case the cert file needs to be imported in this keychain as well. OR you configure boths apps (JIRA & Stash) to use the…

so a previous parent issue-type is a sub-task issue-type now? did you clicked on "More Actions>>Convert to Sub-Task" by accident?

Oh you're right. Sorry for my posting in that case

hi J, no scripting needed to achieve this. install "misc workflow extensions" add a postfunction to the transition "Reopen" and choose "Assign to last role member - Assigns the issue to the last user from the specified role that had this issue assigned before." the only requirement here would be that only assigned useres…

i don't know how licensing works in OnDemand Jira.. but if you need to upgrade jira seats you must adjust the plugins as well to match the same users count. so you can't have a 2000 users Jira license with a 500 users Greenhopper plugin...

you need to do something like this: https://answers.atlassian.com/questions/111216/jira-port-issue/111247 just create a vhost conf file and add something like <Proxy *> Order deny,allow Allow from all </Proxy> SSLProxyEngine On ProxyRequests Off ProxyPreserveHost On ProxyPass / ajp://localhost:8009/ ProxyPassReverse /…

hi. https://confluence.atlassian.com/display/DOC/Working+with+Attachments this one is not working for you? that the server may be unavailable could be caused by an timeout wich you run into due to file size problem. can you provide some more details? log lines are always welcome to nail down the issue

Ok. But now it is in a new keystore in root/. You must tell tomcat which one to use now cause by default it is inside your confluence_dir/jre/security/lib/cacerts if i remember it right

maybe this solution will work for you http://www.lumension.com/kb/Home/Patch-and-Remediation/Importing-a-Certificate-results-in-Keytool-Error-(.aspx

ok i found another way...lets stick with the p7b keytool -import -trustcacerts -alias server -file star_domain_com.p7b -keystore <keystore_name> can you try thisone please? ps: use comment

ok. please run this on your box openssl pkcs7 -chain -print_certs -in star_domain_com.p7b -out star_domain_com.cer afterwards try importing the cer file. let me know how it goes please note: i am not 100% if this will work for you...but i remember not facing any issues using .cer or .crt files...so lets try converting…

I see. Do you try to import the csr?Thats only the signing request file and not a certificate

hey charles... how was the cert file created?

Hi Deasn, there are several possible extensions that may fit your needs. look for "release management" on https://marketplace.atlassian.com the workflow thing can be done manually by yourself as well.. i.e. just add a transition called "Approve" and make it only be accessable by specific group/role/users... set up the next…

was caused by a third-party plugin.

Hi Jaro, you mean sth like this? https://confluence.atlassian.com/display/GH/Configuring+Quick+Filters

I am kinda confused here. As you are talkin about workflows you may mix sth up ?Please clearify if this isn't maybe a transition thing. If so just add 2 transitions and configure a condition to each of them. Sth like "only show if..."Maybe you will need to install additional plugins to get…

i hear you renjith. just was wondering if it might be possible cause i also had an solution like this with "Clone" function from inside "More Actions" https://answers.atlassian.com/questions/114724/how-to-modify-this-code-to-add-restrictions-to-a-projectrole

well unfortunately that's not that easy..as you can read in the feature request i've posted above. this is not a feature of jira and nobody knows if or when it will be integrated. i am not sure but i think you could put some javascript inside a velocity processed message field to hide some sub-task issuetypes if the parent…

i see this was requested long time ago https://jira.atlassian.com/browse/JRA-7990

i think i've seen some question like this here before. i believe the goal is to seperate the possibile sub-task issue-types depending on what the parent issue-type is. am i right? so lets check this scenario...maybe other will understand that one better Issue-Types (Parent) "Story" "Bug" Issue-Types (Subtask) "story task"…

ok. can you access your database manually using the confluence credentials? btw...what browser you use during the setup?

to me it looks like you have some issues saving the confluence.cfg.xml Unable to move C:\Program Files\Atlassian\Application Data\Confluence\confluence.cfg.xml2155273733698608188tmp to C:\Program Files\Atlassian\Application Data\Confluence\confluence.cfg.xml. Falling back to non-atomic overwrite. this shouldn't be an DB…

just imagine... filters could contain queries on more than only one project.... how should the import procedure validate that all dependencies are met to be able importing filters or dashboards (using filters etc...) i.e. if only one project or issue-type doesn't exist that is used in your jql the filter is useless anyway.…

exactly. thats what i suggested 35 mins before ;) use a custom field unless a status like i.e. "En Procés" is no detail enough for your customers to show that your team is actually working on the issue. setting the resolution means you have finished working on the issue and the resolution is ${available value} you really…

well that sounds good. now i start wondering why it didn't work for me when i tested it before :)

yeah that's exactly what i did too. i know about the positions of postfunctions so i already placed the update between the two default entries...my issues was created but resolution was unresolved. i was tryin on 5.2.7

so this describes exactly what nic said. your created issue should show "En Procés" as default value for the field "Resolution" this can't be done without doing changes that will affect your entire instance. I really do think you want to change "unresolved" to display as "En Proces", unless you want Jira to think that…