Task #11794 (new)
Opened 10 years ago
Last modified 8 years ago
Bug: Insight configuration rejects distinct configs
Reported by: | drussell-x | Owned by: | jburel |
---|---|---|---|
Priority: | minor | Milestone: | Unscheduled |
Component: | Insight | Version: | 4.4.9 |
Keywords: | n.a. | Cc: | spli, mtbcarroll |
Resources: | n.a. | Referenced By: | n.a. |
References: | n.a. | Remaining Time: | n.a. |
Sprint: | n.a. |
Description
These are distinct configs:
myserver.mydomain.com 4064
myserver.mydomain.com 14064
I think the configuration dialogue is checking only the server name for distinctness as when the second config is entered it does not get added.
Change History (8)
comment:1 Changed 10 years ago by jburel
- Cc spli added
- Milestone changed from Unscheduled to 5.0.0-beta3
comment:2 Changed 10 years ago by spli
comment:3 Changed 10 years ago by drussell-x
Also, this will have to be represented in the list of servers either by assigning names to each config, or displaying the port number as a part of it (maybe, only if the port is not 4064 so normal users probably never see this)
comment:4 Changed 10 years ago by jamoore
- Summary changed from Insight configuration rejects distinct configs to Bug: Insight configuration rejects distinct configs
J-m: did you want this in a different milestone?
comment:5 Changed 10 years ago by jburel
This is mainly a developer requirement. so I leave it where it is for now.
comment:6 Changed 9 years ago by mtbcarroll
- Cc mtbcarroll added
comment:7 Changed 9 years ago by jburel
- Milestone changed from 5.1.2 to 5.x
comment:8 Changed 8 years ago by jamoore
- Milestone changed from 5.x to Unscheduled
Also reported in #11696