+1 888 340 6572
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
feature_request_small.png
Open Feature request MC-997

Broker Profile selections on same chart don't agree
action_vote_minus_faded.png
0
Votes
 action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Description

It is possible to apply a broker profile to a chart using the Chart Trading hide/show tab and also to apply a broker profile to the same chart using the Strategy Properties option of the Automation button. It is inconceivable that these two settings would ever be set to two different broker profiles on purpose. Instead it offers an opportunity for failure in the automation process if the user (quite logically) thinks that the selection made using Chart Trading has been applied to the chart--when it has not.

Steps to reproduce this issue
  1. Open Chart Trading hide/show window. Select Account #1. Close hide/show window
  2. Click on Automation button>Strategy Properties dropdown menu option. Note that a different account number can be selected. Select Account #2.
  3. Reopen Chart Trading and note that Account #1 is still selected

Standard useability behavior expectations are that if the user is allowed to effect changes to the same data in two separate places in the UI, then those changes should be propagated--and NOT independent.

Comments (0)
icon-mono-settings.png
History
sidebar_collapse.png sidebar_expand.png
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • 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
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
    Critical
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