Skip to main content

#Agile Accelerator0 discutindo

Bug: When adding acceptance criteria on a New Work item on create, if the name exceeds 80 characters there is no warning or block, the work item saves, but there is a toast message that Acceptance Criterion Name: data value too large: user provided very long name for the criterion goes here for testing (max length=80) and the acceptance criterion and any subsequent acceptance criteria fails to save. 

 

It would be great if we just couldn't enter more than 80 characters if that is the limit!  

 

Alternatively, if the lightning components weren't locked so we could copy/override them without reinventing them that would be useful. Thanks!

 

#Agile Accelerator

0/9000

Just a quick tip in case someone else runs into it or Salesforce folks want to investigate: We ran into a bug with the New Work page when accessed via the new Kanban Board or Work tab. If there are no active product tag assignment rules then the lookup fails to populate any options for product tag which makes it impossible to save a user story. Strangely enough, even making one rule active on a product tag seems to make all the active product tags for the team available to select.  

 

Interestingly, this bug does not seem to affect the modal new work popup from the work manager or old kanban board new buttons. 

 

Hint: if you don't want to set a product owner the validation rule can be disabled under setup allowing you to clear the field before saving 

 

#Agile Accelerator

0/9000

Just an FYI That if you use the theme column on the work manager in @Salesforce Agile Accelerator

it breaks the view if any themes are assigned to work. 

 

#Agile Accelerator  #Error

0/9000

We have recently implemented Agile Accelerator and our beginning to build out the solution in a way that works for our team.

We wanted to update the Bug work item lightning record page to be a simpler.

We removed the "Found in Build", "Priority", "Frequency", and "Impact" fields from the record page but now when trying to save a Bug I'm getting the following error:Unable to save a Bug work item due to Error

I've checked validation rules, flows, page layouts, etc. and am not sure how to get this error to not trigger as we aren't using the fields it's triggering for.

 

Thanks in advance!

#Agile Accelerator #Salesforce Admin

5 respostas
  1. 5 de set. de 2025, 18:12

    In theory the priority should be calculated for you by selecting impact and frequency, but yes, if you don't use those fields then this is super annoying. A before save flow could set the value.

0/9000

Burn Charts

Am I completely lost or does Agile Accelerator not have release burn up charts?  If that is the case, any plans to add this functionality?  Or has anyone created their own that they can share details around?

 

Also, has anyone had an issue with the Sprint Burn Down charts?  When I access the sprint burn down from Work Manager, I get a nice, accurate graph.  However, when I use the Sprint Wall and open the charts, the graph is empty (or appears to plot all 0's).

7 comentários
  1. 4 de abr. de 2024, 07:12

    Hey Nicholas,

    I was just working around the AA, could you please help me understand; From where in Work manager do you access the burndown chart?

0/9000

Hi All, we have an older version of Agile Accelerator 1.160, in our Production Org. As I was trying to upgrade the package version I received an error that version 1.161 failed with this Problem: 

 

1.  This app can't be upgraded.

Salesforce has blocked this package upgrade because the new package version removes some Apex code that one or more Visualforce pages or global Visualforce components need in order to function. Please contact your partner with this error information. Provide these component names to your partner. Visualforce Pages: QA_GenerateAnnotations, QA_MassEditTC, qa_tpadddefaultstep2, QA_AddTEToUS, QA_AddTestCases, QA_TCBugsDetail, QA_TEBugsDetail, QA_TPTELibrary, QA_TPQuestionDetails, QA_USTELibrary, QA_addUStoTP, qa_tpadddefaultstep1, QA_AddTCtoUS.

 

Hoping to get some assistance so I can upgrade the package, any help is appreciated! #Agile Accelerator

7 respostas
  1. 3 de ago. de 2023, 17:09

    @Samantha Foster Our last update included some deprecation of older unused files.  These updates were pushed to every org but a tiny percentage are not upgraded if the org is too busy.   To upgrade yourself first update to v1.160.1 with this URL:

     

    https://login.salesforce.com/packaging/installPackage.apexp?p0=04t3l000000Q7LZ

     

    Then upgrade to v 1.161 with this URL:

     

    https://login.salesforce.com/packaging/installPackage.apexp?p0=04t3l000000cVR0

0/9000
9 respostas
  1. 29 de nov. de 2023, 07:56

    For anyone else facing this issue - I came across this issue as well. I did not add a Product tag and attempted to create the new team - "Sample". So, i believe it was a partial transaction and it did not rollback at the back-end, so I was not able to create the team "Sample" again. But later you can go into the Agile Accelerator > Teams tab and select List Views - All, and this would also list the partial team "Sample" that was created and then this can be deleted.! 

     

    Cheers..!! :) 

0/9000

Hello Team, Looking for a quick response/solution. The Sprint wall Kanban board is not coming up and when we try to confirm Forecast we get a lightning component error.

 

We are currently using 1.161 and we tried the same full setup on 1.160.1. But on both versions, we are facing the same issue.

One of our partner teams is using 1.160 and it's working fine for them.

 

Has anyone faced a similar issue and found any solution?

Really appreciate any input.

ThanksSprint Wall Kanban ErrorScreenshot 2023-07-23 at 22.47.32.png

#Agile Accelerator

0/9000

We recently refreshed our development org and I am trying to upload some new work (unrelated to Agile Accelerator) to the org. I am running all tests on validation and getting a number of error messages on a number of ADM classes. Here are a few of the error message:

 

ADM_AgeOfWorkTests | testTotalAgeWhenClosed | System.DmlException: Update failed. First exception on row 0 with id a2V8H000000B8dyUAC; first error: FIELD_CUSTOM_VALIDATION_EXCEPTION, When Status = Closed, the following fields are required: Deployed Resolution, Release Notes, Scheduled Build: []Stack Trace: (agf)ADM_ApplicationApprover_TriggerTest | testApplicationApproverTrigger | System.DmlException: Insert failed. First exception on row 0; first error: REQUIRED_FIELD_MISSING, Required fields are missing: [ProfileId]: [ProfileId]Stack Trace: (agf)

 

When looking at the object I can't find any field called ProfileId, or any reference to a ProfileId for a User. Obviously since the package is managed I can't get inside the code to determine where the issue lies.

 

Any help?

 

#Agile Accelerator #Fields In Agile Accelerator #Agile Accelerator App #SF Agile Accelerator #SF Agile Accelerator

1 resposta
0/9000

I started with 25 objects, and I'm down to these last 4. When I query where the fields are used.. they are not used anywhere, but I am continually seeing this error. I have also done a hard refresh and cleared my cache. The lookup field also has nothing attached to it and the related list is not in use on any layouts. 

 

Any help would be appreciated. #Uninstalled Packages #Agile Accelerator

1 resposta
  1. 8 de set. de 2022, 05:39

    Did you click on these fields? or you should check the first object 

0/9000