Yogesh Mude_u145qk Expert

Hi @markxsimu, Yes, you can Upgrade confluence to latest version ie 6.8.0 without upgrading java. (Yesterday only i have upgraded confluence from v6.5.0 to confluence v6.8.0 and we are using java v 1.8.0_171). you can use the latest version of the confluence with an older java but the java version should be min 1.8 

HI @Helpdesk, Yes, there should be no limit to configure the incoming handler for a project. No, the incoming mail handler should work for bug issue type as well. I have configured for a single and tested as well, please refer below screenshot for the same.

HI @Chandra Khandavalli, Can you attach the screenshot of the configuration what you have configured in Job and which task you have added to it. If possible please share some logs.

HI @maheswaran gurusamy Please check do you have Work on Issue permission or not. For this, you need to Contact your administrator.

HI @ASweeten, Thanks for the response. Yes, we can export the data to a .csv file from Clarizen and I have prepared the file as we want I tried to import in Jira using CSV import in jira and it works perfectly.

HI @Marlon Daniel, Just check your server time on which you have hosted this Jira server.

HI @Amadeo Cuadrado, As u mentioned you only have created this project and the default Issue type screen scheme has been associated with this project so now you wanna change the issue type scheme so just click on the Default issue type Screen scheme and it will redirect you to a new page and select the screen scheme…

hI @Amadeo Cuadrado, Could you please let us know which link you have been clicked hence you are getting Null pointer exception.

Hi @Alexander Perevalov, Please have a look at the Permissions and Restrictions for confluence Space.

Hi @Consulente Atlassian, Better to have single permission Scheme and then work with project roles/groups to restrict the functionality like close issue blah.. The reason is that in feature if you want to change something related to permission then just you need to do the changes in single permission scheme but not in…

HI @Rakesh Negi, If you see in the Image the message will be displayed like the Atlassian Marketplace server not reachable due to the reason you are not able to find the addon. Please find the add-on from Marketplace site and download it and then Upload it from Manage Add-ons.

Yes as mentioned @Ollie Guan Use different workflow for diff issue type and configure the Conditions for particular roles like Developer and Tester.

HI @Itay Keller, You can manage this using Groups. you need to create a group called administrator just add those two users in this group and this administrator group to Global permission Administer Jira so that only these two users will be able to manage the admin functions.

Hi @Rod McWilliams, Yes, please contact your IT team regarding this, they will provide the solution for this. Once you will configure Incoming mail handler, you will get the options like I have shown in my earlier comments image.

HI @Rod McWilliams, You need to use Incoming Mail Handler. Admin --> Mail section -->Incoming Mail --> Add incoming Mail Handler

Hi @Chandana Wijesuriya, Please see the Story Points Context by Default it sets to Epic and Story. https://confluence.atlassian.com/jirakb/unable-to-define-story-points-for-story-issue-type-779158858.html

Hi @Cong Hieu, If you feel these steps are correct/ useful please don't hesitate to Accept the answer.

HI @Chandana Wijesuriya, I think you have not yet configured Story point hence you are not able to to see the estimation over there. For more information story points .

Hi @Rod McWilliams, While creating automation you will not see the reporter field for Edit issue rule why because while setting/ configuring email itself is it asking you to provide the Default Reporter. Whenever issue will create in JSD you want to set the Reporter as a Single person then why can't you set the Default…

Hi @Daniel Moscovici, Please have a look at this article may be this will help you. At bottom, you will find documentation about Bitbucket migration.

Hi @Daniel G, Ok, see the first time when you clone the repo to your working dir/local machine then it will create .git file or we can say it will initialize with that repo. Try to create a new directory into the local machine then cole the repo and see.

Hi @Stephen Nuthall, Have you installed Confluence using Custom installation or Express installation? Can you please check typing this cmd on the terminal and see if the Confluence was started or not. ps -aux | grep java or ps -ef | grep Confluence If the Confluence was started then it should show you the Installation path…

Hi @Ignacio G.Mesones, Does it mean Instance? if yes, Which application you are using and what is the error you are getting?

Hi @Daniel G, Why can't you create one new empty repo and then try to clone and see if still, this error persist?

Hi @Mariana D'Apuzzo, Actually, there is no way without login to Jira and the configuring Outgoing mail in jira you should require system Administrator rights. If you have admin rights then please have a look at this article.

ok, That's fine but what feedback you are going to collect from this Bitbucket/Jenkins? Why I'm asking because anyhow while committing code in bitbucket the changeset and modified files you can see into that particular issue development panel and Jenkins build status in CI Build tab. The basic use of the issue collector…

Please see the vendor Documentation for this.

Hi @Dushyant Kayarkar, Could you please let us know using Jira issue collector what you are going to prove? What do you want to do with this functionality in Bitbucket/Jenkins?

No, You can not hide the request type from issue view screen but you can hide from the portal. While creating an issue from the portal customer will choose the request type and it will show you on issue view screen hence you can not hide it. for more information please use this add-on.

Hi @Rakesh Negi, You can use Nagios integration for Jira free add-on for this.