youngmon/atlassian-qna huggingface dataset:
Auto Moving cards based on time they've been in a certain list?
Asked by Nancy Elizabeth Media:

Hey everyone!

We have a list of "working on" and don't add due dates on our cards unless there is an urgency.  

I would love cards to be flagged or moved or something based on how long they've been in that list?

Is that possible?


Answers:
author: Christl_Email for Trello
body: Hi [@Nancy Elizabeth Media](/t5/user/viewprofilepage/user-id/5042418)? Welcome!

Christl from [SendBoard](https://www.sendboard.com/) here - makers of the [Email for Trello PowerUp](https://trello.com/power-ups/5d4c0b80452f202510cce4cc/sendboard).

I would suggest checking out Trello's [butler automation](https://trello.com/en/guide/automate-anything). You can use butler to label/archive/move cards based on a trigger.

It would depend on what you need exactly, but for example you can automate archiving or moving a card when it's been in a certain list for a certain amount of time.

For example:

![Screenshot 2022-09-30 at 11.26.43.png](https://community.atlassian.com/t5/image/serverpage/image-id/218604i5E14ED54E129763E/image-size/large?v=v2&px=999 "Screenshot 2022-09-30 at 11.26.43.png")

Hope that helps!


author: Genti Tola
body: Hi All!

[Card Time In List](https://trello.com/power-ups/6211e70cf500cc8f17546a80/card-time-in-list) for Trello can be used to track times spent on each list, measuring even previous times it has been on the same list.

It also has plenty of other features like:

- Exports

- Measuring duration to or from due date

- Measuring cumulatuve duration on multiple lists

- and much more...

Cheers!


author: Silvia
body: Welcome [@Nancy Elizabeth Media](/t5/user/viewprofilepage/user-id/5042418)

Silvia from Blue Cat here, we specialize in power-ups that focus on reporting and we love tracking cards in Trello ?

Have you checked our reporting tool? You can easily create a report of cards to see how long they've been in a list. There's no automation to move these cards for you but, you can automate this report to be sent to your email daily or weekly.

When you sign up for a trial with us at [Blue Cat](https://trello.com/power-ups/5d9c90aa18965066fcd44730/reports-by-blue-cat), you can reach out to our support through the app and we are happy to help with creating a report as the above or anything else you might need.
How to run the specific Stage in the Bamboo plan without any dependencies?
Asked by Vinod Kumar:

Hi

We got Bamboo 3.4.2 installed and created the plan with 3 different stages. Each stage will build and create ther seprate EAR. We would like to setup the Bamboo in a way that only one stage or more than one stage can be picked/selected to run the build.

We see there is a dependency between the stages and we are unable to run the specific stage which we would like to run.

How to avaoid the dependency between the stages? or how can we setup the Bamboo plan to pick /select the specific Build task which we would like to execute? Please help.


Answers:
author: Przemek Bruski
body: You can't run Stages selectively. You can create Manual Stages, but you will still have to run all Stages prior to the Manual one(s). As a workaround, you could disable the unneeded jobs, but that's not exactly ideal.

It seems you need to separate out the Stages into three separate Plans.

comments: author: Vinod Kumar
body: Hi

Thank you so much for your reply. Is this not possible in Bamboo 3.4.2 only? or in the latest Bamboo releases as well? Please let me know.

Thanks


author: Przemek Bruski
body: For now, Stages are designed to run sequentially. We may change it in one of the future releases.


author: Juanie Morado
body: Hi,

Running stages selectively (not sequentially) enabled in the what Bamboo release/version please?

Thanks,

Juanie


author: Juanie Morado
body: Hi [@Przemek Bruski](/t5/user/viewprofilepage/user-id/781481) - hope to hear from you soon. Your response will be very appreciated. Thanks.


author: Jaya kumar
body: Hi [@Przemek Bruski](/t5/user/viewprofilepage/user-id/781481) , Running stages selectively (not sequentially) enabled in the what Bamboo release/version please?
User Requirements for Access to Hosted Subversion
Asked by Jeff Bragg:

I've been trying to setup an automated release system, by using Bamboo build plans to orchestrate the required steps to release via Maven's release plugin. To this end, I had created a user within our hosted instance, and put that user in both the users and developers groups. My understanding of the support docs suggested this was the critical factor for read/write access, and I do believe it's at least a piece of the puzzle.

However, adding the user to those groups, and then only granting them application access to Bamboo did not allow that user to do even read-only checkouts. I eventually discovered (by trial-and-error) that granting the user Fisheye/Crucible access allowed checkouts (and checkins). While we can keep these permissions, this user is only meant for automation, and we'd prefer to limit the applications it has access to (especially since extra licensing is required for it to have access to Fisheye/Crucible, which it doesn't otherwise need). For instance, though it needs write access to Subversion (due to requirements of the Maven release plugin), but will never need to make any changes that require code reviews, and really doesn't need access to any of the front-end apps at all.

So is this actually a requirement, to grant application access to Fisheye/Crucible for users that need read/write access to Subversion? Or have I missed some wrinkle that would allow us to do this without such access?

If it is required, may I recommend adding something explicit about that in the user docs, as it just wasn't clear to me, even after attempting to find an answer to this in the various forms of online documentation.


Answers:
author: LucasA
body: Hi Jeff,

Note tha FishEye is an interface to embedded OnDemand Subversion, so Subversion users must have FishEye permissions too.

Regards,

Lucas Lima

Atlassian Support


Tags: cloud

fisheye-crucible-svn-ondemand
automatic builds with branches
Asked by Byron Appelt:

I am using git and I have a branch configured with the "Branch Updater" merge strategy. Changes from my "ci" branch are merged into my "staging" branch and the results are then pushed on the "staging" branch on successful builds.

What I am not sure I understand is how build are triggered. I have the main project setup to poll the repo for changes, bu the changes relevant to this build are on the "ci" branch and it doesn't seem like changes to that branch trigger a new build.


Answers:
author: Przemek Bruski
body: If you have your plan set up on "staging" branch and a Bamboo Branch plan set up on "ci" branch, Branch plan should always get triggered with your commits to ci branch.

Please make sure your build strategy is set up to Poll repository for changes and if it is and your builds don't get triggered - contact support.
How to preconfigure remote bamboo agent exectuables with bamboo-capabilities.properties?
Asked by Jay Barra:

I'm trying to preconfgure remote agents on a machine template so I can clone it out easily when the agents register with Bamboo. I have my bamboo-capabilities.properties file in the bin directory of the remote agent where the agent code runs from and when it does register with Bamboo I see listed the properties I told it about but Bamboo is claiming that the agent can't run any jobs that it should.

So I have several lines similar to this

```
system.builder.Command.NSIS=C:\\Program Files\\NSIS\\makensis.exesystem.builder.Command.doxygen=C:\\Program Files\\doxygen\\doxygen.exe
```

And I see when registered that the agent came up with those properties in it automatically when registering. But Bamboo thinks that the agent does not meet the requirements of any plans.

Is there a separate tag for registering exectuables?

<https://confluence.atlassian.com/display/BAMBOO/Configuring+remote+agent+capabilities+using+bamboo-capabilities.properties>

edit:

In the capabilties page there are now duplicates for the capabilities I configured to be detected automatically.


Answers:
author: Daniel Reiter
body: I had the same problem.

[](https://confluence.atlassian.com/display/BAMBOO/Configuring+remote+agent+capabilities+using+bamboo-capabilities.properties)<https://confluence.atlassian.com/display/BAMBOO/Configuring+remote+agent+capabilities+using+bamboo-capabilities.properties>

The comment from Ramonski (6. August) fixed the problem in my case. Try to make a space before and after the equal sign.


author: Przemek Bruski
body: What do the Job requirements say? It should highlight the unmatched requirements.

Also which version of Bamboo is it? If it has tasks, you're probably better off defining inline script tasks that would just execute these commands (you can use the capability in the script body, it will be substituted).

comments: author: Jay Barra
body: Bamboo 4.0. The tasks are exectuable tasks that I am trying to launch.

I have other agents that can run it, but I have them disabled while I was trying to get this template machine working. It shows the disabled agents as capable or running the plans.


author: Przemek Bruski
body: Does it work if you restart the agent after it performs the initial registration?


author: Jay Barra
body: No, restarting the agent did not fix it. For now I'll just have to manually add all of the capabilties and not use that file.


Tags: executable

property

remote-agent
How to deploy from Bamboo using Git?
Asked by Joe Song:

How can I deploy from OnDemand Bamboo to an external server via a Git repo?

What I had envisioned was:

1. Have Bamboo checkout a branch from the Git repo (on Bitbucket if that matters).
2. Run targets from a build.xml file stored in the repo, these targets would run Unit Tests or minimize CSS and JS files. In other words, perform some actions on the files.
3. On build success, create a zip artifact or create a new tag and commit that to the repo.
4. Have Bamboo connect, maybe via SSH, to the web host and execute a Git pull to update the code on the server.

The problem seems to be that, because I'm using Git, I can't push back to the repo as I want to do in #3. Then, I don't have a way to connect to the web host to execute the pull because I can't seem to automate an SSH call that uses user/pass credentials.

Am I thinking about this wrong? Is this possible in a downloaded instance but not in OnDemand? Am I missing something obvious?


Answers:
author: Przemek Bruski
body: Joe, there shouldn't be any difference.

"Push tag" part

On OnDemand, the checkout will be made from HTTP url, so no credentials will be available to the agent and you need to make sure they're there.

Also, like all checkouts made against a specific revision, your checkout may be a 'detached head' checkout, meaning that you need to make sure you're repo is appropriately synced with origin so that the tag/push call suceeds.

Finally, IIRC, the repository will have no origin defined, so you need to specify the push destination.

"Pull" part

If you use HTTPs access for pull, you can inject user/pass directly into the URL - this is the simplest method.

Otherwise, you need to make sure you SSH has access to credentials you want to use.

comments: author: Joe Song
body: I think I follow most of that, but what I realized is I can do almost all of it through running scripts as a task in the build. What I'm still stuck on, however, is connecting to the webhost server via SSH. The only way I could figure out to do it was to install the SSH plugin from Atlassian Labs, but of course you can't install a plugin in the OD instance.

Maybe I should put it this way: how can I run commands on a remote server from a OD Bamboo task?


Tags: cloud
Bamboo ignoring changes in atlassian-user.xml
Asked by David Corley:

We're testing a switchover from LDAP to AD.

We've reconfigured the atlassian-user.xml to use the AD connection and user/group settings. We've test these settings with Paddle to ensure everything is correct, but when we try to use Bamboo, we can only login with the old LDAP credentials!

There must be a persisted cache somewhere (we've restarted Bamboo after changing atlassian-user.xml), so can someone tell me how to completely flush any user/group cache that might exist?


Answers:
author: David Corley
body: Never mind. atlassian-user.xml was in wrong location


Tags: active-directory

atlassian-user.xml

ldap
Bulk change bamboo plan labels
Asked by Patrick Phelan:

We have a huge amount of plans in bamboo (400+) and I'd like to be able to give them all labels so we can use the filtering functionality better. I don't see a way of doing this as a bulk operation however.

I saw in the rest api documentation that you can change the plan-build labels and I altered this call to try and change the plan labels. The command worked ok. Retrieving the labels after the change showed the label was added but this wasn't reflected on the web ui. (I added the label "test" and it did show up in the filter options but the plan didn't show the label and when the filter was selected there were zero plans shown)

Curl command I used:

```
curl -k -v -X POST --user &lt;USER&gt;:&lt;PASSWORD&gt; "&lt;BAMBOO-URL&gt;/rest/api/latest/plan/&lt;PLAN-NAME&gt;/label" -d "&lt;?xml version=\"1.0\" encoding=\"UTF-8\" standalone=\"yes\"?&gt;&lt;label name=\"test\"/&gt;" -H "Content-type: application/xml"
```

Any ideas on an alternative to going in to 400+ plans and adding labels one by one?


Answers:
author: PiotrA
body: Cool, thanks for checking that. I've raised <https://jira.atlassian.com/browse/BAM-11960> for that bug. Feel free to add yourself as a watcher to it if you'd be interested in solving the issue.

cheers!


author: Patrick Phelan
body: Yes, that worked.

1. Added "test" label with REST

2. UI does not display label

3. Changed plan configuration name

4. Saved. Label now displays


author: PiotrA
body: What would happen if you:

1) used REST to add a 'test' label to a plan that has no such label.

1a) check in the UI if the 'test' label appear - we expect it won't appear, while it will be in the db table.

2) edited configuration of that plan and saved it (for example changed the plan name from "Plan name" to "Plan name2")

3) would the 'test' label appear in the UI?


author: Patrick Phelan
body: Yes, the manual editing of a plan and adding a label on the UI works fine. Using the rest api, I can see the change going in fine in to the buildresultsummary_label database table. Except it needs a restart of bamboo for that change to be picked up on the UI.

As I said, it shows up in the list of labels to filter but it doesn't seem to be attached to the plan.


author: PiotrA
body: Hi Patrick,

I wonder if editing labelled plan configuration (and saving it) would be enough for Bamboo to start displaying the labels in the UI. Would you be able to check that on a single plan? I think you've encountered a bug (obviously) but above test could narrow down where the problem exists in the Bamboo code...

cheers!


author: Patrick Phelan
body: After further investigation, this command above actually works. But it doesn't show up on the web front end until after a reboot of the bamboo service.
Is it possible to set the AWS region to EU in Bamboo?
Asked by operations:

Just ran through the configuration and setup for Bamboo and didn't notice any mention of AWS Region. When started the first build it created the instances in US (Virginia). It would be more convient for us if we could change this to specify EU region as it takes quite a while to download.

Thanks


Answers:
author: Przemek Bruski
body: Unfortunately it's not possible at the moment. Please [vote here](https://jira.atlassian.com/browse/BAM-9515).


Tags: aws
Cannot recreate project / plan after deleting all plans
Asked by Martin Filteau:

I've deleted all projects / plan using Admistration-\>Remove Plans

After that, I cannot create a plan with a project name or key of a previously deleted project.

The Create New Plan form validation insists on the fact that the project name / key already exist.

The problem is that I cannot create the plan specifying this project since all have been deleted.

How do I clean up a Bamboo server?


Answers:
author: John Knight
body: See <https://jira.atlassian.com/browse/BAM-10174> - plan deletion is a background task and there's a couple open issues around providing better notifications on deletion.
Filter by Project
Asked by gbonk:

Could bamboo have a feature to filter out the dashbord by Project instead of plan? We have 100s of projects but most people are only interested in a couple of them.


Answers:
author: James Dumay
body: Hi gbonk,

You should be able todo this with Dashboard labels. See [this blog post](http://blogs.atlassian.com/2011/11/dashboard-filtering-with-labels/) :)

Thanks  
James

comments: author: gbonk
body: I could do that if I wanted to tag 100s of plans and then also I would have to rememeber to tag new plans. This is the same issue I have with the "favorites"... when I look at My Bamboo some plans are missing because then I have to explicitly favorite them.

I want and easy way to explictly "favourite" 4 of our projects out of 100+ projects and 1000s of plans. Then I would only see four projects on the "All Plans" This would need to be a new feature it appears.

So if I could show only the projects that I want and ALL of the plans w/o any additional interaction ( maybe filter out disabled ones too ).


author: Cameron Ferguson
body: @gbonk,

I've mentioned this before as well. Labels are nice in some regards, but they certainly don't help achieve everything that you want as easily as you should be able to do it in my opinion. One of the issues I've found with labeling has been that if you label an existing plan, that's only going to tag new builds. All the older builds need to be manually re-labeled. The labels working like this do provide some advantages for certain situations, but not as a general "project filter" like you and I are both wanting to see.

For us I'd like to see projects fall under "suites" of software. We could assign a particular project to an overall "Suite" that you set up. This ideally would give you tabs across the top of the navigation area that would contain your plans and all their builds. This idea is a bit beyond the traditional "Labeling" idea.
General Question About OnDemand Capability
Asked by Luke Majewski:

I'm recently getting back into Bamboo and would like a clarification on capability. I do not think what I need is possible in OnDemand, however I think it's possible with Bamboo with some plugin(s).

I will be deploying a PHP app to EC2 and would like to know whether Bamboo can handle push-button (automated, scripted) deploys. My understanding after reading through the blogs, forums, and user manuals is that OnDemand would not be suitable for this application. However, using Bamboo with something like DeployIt would work.

Can someone confirm or correct the above assumptions?


Answers:
author: Luke Majewski
body: Hi Przemek,

Thanks for responding so quickly. I realize OnDemand cannot use third party plugins, hence my general question of whether Bamboo (OnDemand or otherwise) can deploy to EC2 without 3rd party plugins.

I guess it boils down to - it appears Bamboo would be able to deploy to EC2 (when I say deploy I mean a staging or production instance of the application) based on reading the blogs however I cannot find a clear answer in the documentation. Could you possible point me to the appropriate materials so I can begin trying to demo this internally?

Cheers,

Luke

comments: author: Przemek Bruski
body: It all depends how you perform your deployment. If you have it scripted or run a 3rd party app to do it, you don't need a plugin - you can execute scripts or 3rd party applications using standard Bamboo Tasks - OnDemand or not.


author: Przemek Bruski
body: If you need a 3rd party Bamboo plugin for your deployment, you can't do it with OnDemand. Other than that (scripted deployments using custom/3rd party tools) there should be no difference between OD and Standalone during deplyments.


Tags: cloud
Prevent bamboo re-index on upgrade
Asked by gbonk:

We're way behind in upgrades to bamboo. We're going to do a pregressive upgrade, stepping through each minor upgrade. Some of the upgrades will force a re-index to occurr, where we don't care as we're not going to be on that version for more that 5 minuntes before we shut it down and upgrade to the next version.

Is there anyway in the upgrade startup for a bamboo config where we could block the forced re-index ?


Answers:
author: Przemek Bruski
body: You can't block it. But going through each minor version is not the recommended upgrade approach.

If you follow the Bamboo upgrade documentation and upgrade only to the required interm versions, there'll be only one reindex when you upgrade to the latest version.

comments: author: Przemek Bruski
body: BTW. I've checked and it seems that recently there's been only one forced reindex in the ugprade tasks - still, I'd recommend doing the upgrade as recommended in the upgrade guide.


author: gbonk
body: Thanks. Maybe I'm not using the right terminology saying "minor" and I  
believe I had followed the upgrade guide to the letter.  

We were pretty far behind so I had quite a few upgrades to make to get  
current. I followed this progression of versions...  

2.5.5  
2.6.3  
2.7.4  
3.0.5  
3.1.4  
3.2.2  
3.3.4  
3.4.5  
4.0.1  
4.1.2  

There were two forced re-indexes. I did note in the later release notes  
that it did say if a re-index was going to be required.  

Please let me know if this wasn't correct ( though it worked like a charm )  

Also there really are not any explicit "upgrade" instructions when it  
comes to the agent on a locally hosted machine that I saw, so I wasn't sure  
what to do or how to do it, but after a couple of tries I figured it out.  

Thanks.


author: Przemek Bruski
body: That's a LOT of work...

Strictly speaking, the approach you've taken was not incorrect. The recommended approach is to follow [the upgrade guide](https://confluence.atlassian.com/display/BAMBOO/Bamboo+4.1+Upgrade+Guide), section "Notes for upgrading from a version of Bamboo prior to 2.7.4", which in your case means that you only needed to upgrade to 2.6.3, then to 2.7.4 and then directly to 4.1.2 .

The problem with upgrading through all releases is that an upgrade task may be buggy in, say, 3.1.4 and fixed in 3.4.x - which means that going directly to 4.1.2 already uses the correct task.

You don't need anything to upgrade agents - be it local or remote.


author: gbonk
body: I understand that now that "You don't need anything to upgrade agents" but it would have been nice if the docs had at least said that :-)
Access to network drives in Bamboo
Asked by AmitB:

I am unable to write data into network drives using atlassian command. In particular, when I finish building our code and generate the installer (using nsis), I wish to write the final installer exe to a shared network drive. I get an error saying I don't have access to the drive. Is this a known limitation?


Answers:
author: AmitB
body: Looks like Bamboo does not recognize drive letters. Providing a full ip address works (i.e. \\\\100.0.0.1\\)


author: tkhduracell
body: Mapping seems to be session based. If you map the networkdrive using bamboo (scripttask) is seems to work fine.