Uploaded image for project: 'Advanced Roadmaps'
  1. Advanced Roadmaps
  2. JPOSERVER-350

Exception "Error in variable slot function" when assigning Stages.

This issue belongs to an archived project. You can view it, but you can't modify it. Learn more

    XMLWordPrintable

Details

    Description

      NOTE: This bug report is for JIRA Portfolio Server. Using JIRA Portfolio Cloud? See the corresponding bug report.

      Exception timestamp: 1431545652817
      
      java.lang.RuntimeException :error in variable slot function 

      Error when assigning team members to stage.

      Steps to Reproduce:

      1. Create new scrum plan: “Test Plan”
      2. Configure Stages and Skills

      • Stage 1
        • Skill 11
        • Skill 12
        • Skill 13
      • Stage 2
      • * Skill 21
      • * Skill 22
      • * Skill 23

      3. Create Team and assign some members

      • Team 1

      4. Import backlog
      5. Assign Stages to Team (find screen-shot)

      Click on "Recalculate" and get the following error message.

      Exception timestamp: 1431545652817
      
      java.lang.RuntimeException :error in variable slot function
      
        at com.radiantminds.roadmap.common.scheduling.trafo.teams.common.sprints.VariableScrumWorkSlots.findInIrregulars:69
        at com.radiantminds.roadmap.common.scheduling.trafo.teams.common.sprints.VariableScrumWorkSlots.getSlotOrNextForTimeStep:50
        at com.radiantminds.roadmap.scheduling.data.resources.ResourceGroup.getSlotOrNextForTimeStep:123
        at com.radiantminds.roadmap.common.scheduling.retrafo.stats.ScheduleStatisticsProvider.getPartialSlotData:79
        at com.radiantminds.roadmap.common.scheduling.retrafo.stats.ScheduleStatisticsProvider.calculateScheduleStatistics:63
        at com.radiantminds.roadmap.common.scheduling.retrafo.solution.RoadmapToPlanSolutionTransformer.transform:49
        at com.radiantminds.roadmap.common.scheduling.LocalCalculationProcess.execute:109
        at com.radiantminds.roadmap.common.scheduling.Calculation$2.run:135
        at java.util.concurrent.Executors$RunnableAdapter.call:511
        at java.util.concurrent.FutureTask.run:266
        at java.util.concurrent.ThreadPoolExecutor.runWorker:1142
        at java.util.concurrent.ThreadPoolExecutor$Worker.run:617
        at java.lang.Thread.run:745
      

      Workaround 1

      Make sure at least one of your epics or stories can be scheduled, which means it must have an estimation and there must be at least one team available with members providing the needed skills.

      Workaround 2

      If workaround 1 does not work, additionally adding another release in the stream, will clear out the error in some cases

      Attachments

        1. DBSync UI Re-Design.xml
          42 kB
        2. Exception.txt
          3 kB
        3. Screen Shot 2015-05-13 at 16.29.56.png
          Screen Shot 2015-05-13 at 16.29.56.png
          60 kB
        4. Screen Shot 2015-05-13 at 16.34.17.png
          Screen Shot 2015-05-13 at 16.34.17.png
          48 kB

        Issue Links

          Activity

            People

              Unassigned Unassigned
              pjunior Paulo Junior (Inactive)
              Archiver:
              atibrewal@atlassian.com Aakrity Tibrewal

              Dates

                Created:
                Updated:
                Resolved:
                Archived: