Daniel Santos_157bm4 Atlassian Team

Hi @David FALLAS, Let me share some troubleshooting tips that might help you moving forward: * First of all, check what part of the build is reporting this error: * What is the affected task? * It it is an script task, or a task that uses an external builder or script, check specifically what command is failing. * Try to…

Hi @[deleted], Bamboo deployments are designed in such a way that only specific branches are configured to deploy. You are able to configure multiple branches by setting extra triggers on your deployment environments, but that is a manual task. This configuration is described in this document: Deployments from branches -…

Hi Toni, Usually, this happens because Bamboo is not finding its home directory or the home directory does not have the database configuration properly set. This scenario triggers the installation wizard so a new installation can be set. If you had an installation working before and you want to restore it, you need to make…

Hi @Eric Pederson, I'm glad you found the correct regex pattern to filter the commits =] If you don't mind on accepting my answer above, that will help other community users to see that this question is solved. Thank you for sharing your configuration an tests! That helps a lot the community.

Hi @Eric Pederson, You can achieve this in Bamboo as well through the Plan/linked repository settings at: If the regular expression in the Exclude changesets field matches the commit message, that commit will not trigger a build nor be tracked in Bamboo build results.

Hi @Karel Vervaeke, The answer to your question is in this community thread: Bamboo REST API to retrieve repositories of the plan

Hi Brian, You should be able to find a reference between each release and the build used to create it through the Bamboo UI (Deploy >> All deployment projects >> (YOUR_DEPLOYMENT) >> Releases). Is that enough for your team to discover the right build? If you want you can also carry the build number in your revision string…

Hello @byoung_novetta, I do recommend you to use the auto incremented release version feature as described in this page: Naming versions for deployment releases - Atlassian Documentation. You will also be able to use variables to compose the version, but the last number should be defined in the deployment configuration so…

Hi @Development GGN, Please refer to your first question for suggestions on troubleshooting. That one was selected because it contains a better description of the problem. Thank you!

Hello @Development GGN, The main build blocks that could play a part on this issue are: * the Bamboo server * the network devices/software intermediating the connection * the Browser In order to cover them and identify what is causing this problem we suggest you check: * Check the Tomcat server logs. They should tell you…

Hello Mike, I've checked the errors you were experiencing and this is what they usually mean: Invalid URL: Domain unreachable. This error is misleading, it was reported as an enhancement but closed due to missing information - #12533 - Urls that don't exist give unclear "invalid url" error - Bitbucket. I've added some…

That is observed to be true for Bamboo 6.4.1, but not necessary for newer versions of Bamboo like 6.6.1 (which is the one I tested).

Hello Irfan, You cannot checkout only the modified files using the Source Code Checkout task, you will need a script task for this. The challenge is more related to git than Bamboo itself. I was able to get it working with the following approach: * Create a plan with the repository you want to checkout and make sure the…

Hello Torsten, I think you are right. From your description, It seems you've stumbled into this bug: [BAM\-18460\] New plan branch is automatically deleted due to last commit date from the newly created branch. As a workaround, I do suggest that when you create a new branch from a commit that is older than your expiry…

Hey Sumit, can you give us more details about this problem? What task are you using to parse your tests? How your report is generated? If this is Junit parser, please check this link: JUnit Parser task in Bamboo shows 'Failed to parse test result file' error when parsing test results file

Just to register here, the Assign to me gadget only show issues for projects/issueTypes that show the Resolution field. If you hide the Resolution field (from field onfiguration) even the open issues will not be shown in the gadget.

Hi Ghazi, Let's supose these are your LDAP locations to the users: OU=OU1,DC=intern,DC=company,DC=com OU=OU2,DC=intern,DC=company,DC=com And these are the LDAP locations to your groups: DC=groups,DC=company,DC=com Your LDAP Base DN should be the common part ot all locations, complemented to the specific location for users…

Hello, This thread is a bit old but this KB is new and may help someone. https://confluence.atlassian.com/display/JIRAKB/How+to+reset+the+project+counter+after+moving+issues When there are moved issues another table needs to be changed, the moved_issue_key.

Hi Mike, You could use REST API for that. You could make a call like this: https://<jira-host>/rest/api/2/user/permission/search?username&permissions=BROWSE&projectKey=PROJ&startAt=0&maxResults=1000 This is the REST API documentation: https://docs.atlassian.com/jira/REST/latest/ You can use multiple permissions in one call…

Just to update, the 'JIRA Classic' is now called 'JIRA Default Schemes' after JIRA 6.4

Hi, If this is a cloud instance you will need to open a ticket to solve this problem. If this is a server instance and you want to further investigate this problem, you can check the application logs to see what is the error you get from there. This link says where you can find the server logs: Where are the application…

You are welcome! :)

You need to investigate the JIRA log files from <JIRA_INSTALL>/logs or <JIRA_HOME>/log to get a good clue about your problem. Probably the information you need is at atlassian-jira.log file in the <JIRA_HOME>/log. Also take a look at this KB that may be related to your problem.…

Hi, The users and groups in LDAP are separated objects. The Base DN is the root location for JIRA to search in the AD. When you leave the User DN blank you tell JIRA to search all users from that Base DN root, if your search pattern is default. When you specify the Base DN to the specific group path is expected to get only…

Hello, If I understood you correctly you can achieve by installing this add-on: https://marketplace.atlassian.com/plugins/com.idalko.jira.plugins.igrid If not please give us more details of what you want to achieve.

What makes you think you could not use?Which is your JIRA version? Are you using Agile? Are you talking about JIRA Software license (JIRA7)?Please give us more information

Hello Assia, I think you will need to dig into jira-onboarding-assets-plugin-xxx.jar to understand how the Quick Tour work and than modify it. If you just decide to disable it, this is how you can do it: How to Disable User Onboarding in JIRA 6.4

Yes, Nic is correct you cannot perform a partial search for components, but you can search for their complete names. This is an example: Project = JIRA and Component in (“Full name [CN]”, "Full name [IR]") You can find more details at: Advanced Searching - Component

Hello Christian, You could get this information from the database from the following query: SELECT concat(po.pkey, '-', ji.issuenum) issuekey, ist.pname Status, ji.created Issue_Create, ja.actiontype Action_Type, ja.updated Action_Update, ja.actionbodyFROM jiraaction ja LEFT JOIN jiraissue ji ON ja.issueid=ji.id LEFT JOIN…

Hi John, The base DN is the common path for both group and user objects. So if you use: Base DN: ou=memberlist,ou=ibmgroups,o=ibm.com Additional User DN: Jira will start to search for users at cn=<ParticularGroup>,ou=memberlist,ou=ibmgroups,o=ibm.com, but you may not have user objects there. User objects are different from…