Workspace name variable

[Greg Carr]

Enterprise user here...we have several large projects around the US and each has its own workspace named after the project and project number.  Within each workspace we have two boards that manage the schedule of work to be performed.  These boards are standardized across all workspaces.  There are a few instances where we want to notify the executive leadership of certain card changes within a workspace but have yet to find a dynamic field that returns the workspace name.  We can send the notification but since the board and list names are identical across all workspaces there is no indication of which project the notification originated. 

Does such a field exist?

[Vongsawat]

There's technically {boardid} which is unique to the board... but not particularly readable, as well as {boardlink}.

But there doesn't seem to be a Variable for the workspace name itself.

There're some workarounds, with drawbacks:

1) Just hardcode the name in to the rule/report. Not the most scalable or maintenance-friendly solution.

2) Have a reference board somewhere. Populate it with a card for each board. Name each card the Board ID, and in the description put in the name of the workspace. Now you can Lookup a Card named {boardid} on ReferenceBoard, and reference the workspace name via {foundcarddescription}. Pain point being that you have to make a new reference every time a new workspace/board is set up, but at least its all in one place.

3) Just have a card on your board named "Workspace Reference" and set the description to the name of the workspace. Then Lookup a Card named "Workspace Reference" (on this board), and reference {foundcarddescription}. Less setup but also specific to each board.

[Greg Carr]

I like your workarounds and will give them a try.  

The notification is triggered by a card move into a specific list.  Our current workaround is a dormant label in the card template with the Project Name as an identifier.  

when a card is added to list "Done", add the dark black "XYZ Logistics test project" label to the card, and send an email notification to every member on the board with subject "Project {cardlabels} alert" and message "The intent of the Work Package environment is to sequence work in such a way that there are no activities put on \"Hold\" or \"Delayed\". When delays happen, it is imperative that Executive leadership is alerted to a potential cost variance."

The problem with variable {cardlabels} is that no other labels can be added to the card. These cards represent work scope and move through workflow lists that represent various stages of the project.  Lables are a great way to highlight progress.