...
You have been editing a plan notification, but the edits seemingly do not take affect.
System and deployment notifications do not seem to be affected.
Solution
This problem is caused by a severe Bamboo bug that will be addressed in Bamboo 5.15.0, refer to the following issues for details:
| Jira Legacy |
|---|
| server | Atlassian JIRA |
|---|
| serverId | 144880e9-a353-312f-9412-ed028e8166fa |
|---|
| key | BAM-17349 |
|---|
|
| Jira Legacy |
|---|
| server | Atlassian JIRA |
|---|
| serverId | 144880e9-a353-312f-9412-ed028e8166fa |
|---|
| key | BAM-17355 |
|---|
|
| Jira Legacy |
|---|
| server | Atlassian JIRA |
|---|
| serverId | 144880e9-a353-312f-9412-ed028e8166fa |
|---|
| key | BAM-17747 |
|---|
|
The only available solution is updating to Bamboo 5.15.0 – meanwhile you need to apply one of the workarounds mentioned in those issues, for example:
Workaround
| Panel |
|---|
|
You may be able to work around this issue as follows: Add an arbitrary new dummy notification (for example, notify a User and select yourself). The notification list should now surface your intended edit on the original notification. Delete the dummy notification again.
|
Related articles
| Filter by label (Content by label) |
|---|
| showLabels | false |
|---|
| max | 5 |
|---|
| spaces | UAAKB |
|---|
| sort | modified |
|---|
| showSpace | false |
|---|
|
...
| | reverse | true |
|---|
| type | page |
|---|
| cql | label in ( "bamboo" , "plan" , "automation-with-aws" , "notification" ) and type = "page" and space = "UAAKB" |
|---|
| labels | automation-with-aws plan notification bamboo |
|---|
|
