Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-3611

Duplicate results when filtering services by service meta data

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 4.10.0-b1
    • Fix Version/s: 4.10.0
    • Component/s: Staff Interface
    • Labels:
      None

      Description

      When filtering by service meta, it's possible to get duplicates. There is really only 1 service called blesta.uk in the attached example, but it appears twice. I assume this is because there is a match on multiple service fields (username & domain).

        Activity

        admin Paul Phillips created issue -
        admin Paul Phillips made changes -
        Field Original Value New Value
        Rank Ranked higher
        jonathan Jonathan Reissmueller made changes -
        Sprint 4.11.0 Sprint 1 [ 108 ]
        jonathan Jonathan Reissmueller made changes -
        Rank Ranked lower
        abdy Abdy Franco made changes -
        Assignee Abdy Franco [ abdy ]
        Automated transition triggered when Abdy Franco created a branch in Stash -
        Status Open [ 1 ] In Progress [ 3 ]
        Automated transition triggered when Abdy Franco created pull request #872 in Stash -
        Status In Progress [ 3 ] In Review [ 5 ]
        Resolution Fixed [ 1 ]
        abdy Abdy Franco made changes -
        Remaining Estimate 0 minutes [ 0 ]
        Time Spent 19 minutes [ 1140 ]
        Worklog Id 13640 [ 13640 ]
        abdy Abdy Franco made changes -
        Time Spent 19 minutes [ 1140 ] 23 minutes [ 1380 ]
        Worklog Id 13642 [ 13642 ]
        Automated transition triggered when Jonathan Reissmueller merged pull request #873 in Stash -
        Status In Review [ 5 ] Closed [ 6 ]

          People

          • Assignee:
            abdy Abdy Franco
            Reporter:
            admin Paul Phillips
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:
              Fix Release Date:
              26/May/20

              Time Tracking

              Estimated:
              Original Estimate - Not Specified
              Not Specified
              Remaining:
              Remaining Estimate - 0 minutes
              0m
              Logged:
              Time Spent - 23 minutes
              23m

                Agile