+1 888 340 6572 Try free for 30 days
MultiCharts Project Management
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Open Feature request MC-678

Selecting "Optimize" clears prior optimization reports

Go to the next issue (open or closed)
Go to the next open issue

I have a feature request concerning the Portfolio Backtester. I will often do the following:

  1. Run a long optimization in Portfolio Backtester.
  2. View the resulting optimization report.
  3. Close the optimization report.
  4. Click on the "optimize" button a second time.
  5. Hit "cancel" without performing another optimization.

After I do steps 4-5, Portfolio Backtester clears the prior optimization report. I.e., the "View Optimization Report" command is grayed out and can't be selected.

This is a headache. Sometimes I'll inadvertently hit the "Optimize" button when I instead meant to select "Backtest." Other times, I'll hit the "Optimize" button to remind myself of what optimization parameters I used to perform the optimization. In either case, I can't go back to my completed optimization report -- I'll have to start over and perform the same optimization a second time.

It would be better if MultiCharts didn't discard the first optimization report until the user selects "OK" and actually begins a second optimization. That way, if the user instead selects "cancel," the prior results are still available.

Steps to reproduce this issue

See above.

Comments (0)
Issue basics
  • Type of issue
    Feature request
  • Category
  • Targeted for
    Not determined
  • Status
    Under Review
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (3)
People involved
  • Posted by
    user-offline.png  Xyzzy (Xyzzy)
  • Owned by
    Not owned by anyone
  • Assigned to
    Not assigned to anyone
  • Subscribers
    1 subscriber(s)
    Click here to show the list of subscribers
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates