Skip to content
GitLab Next
  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • GitLab FOSS GitLab FOSS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 0
    • Merge requests 0
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

Scheduled maintenance on the database layer will take place on 2022-07-02. We expect GitLab.com to be unavailable for up to 2 hours starting from 06:00 UTC. Kindly follow our status page for updates and read more in our blog post.

  • GitLab.org
  • GitLab FOSSGitLab FOSS
  • Merge requests
  • !6110

Fix sorting issues by "last updated" after import from GitHub

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Douglas Barbosa Alexandre requested to merge 21567-fix-sorting-issues-by-last-updated-after-import-from-github into master Aug 30, 2016
  • Overview 8
  • Commits 3
  • Pipelines 1
  • Changes 8

What does this MR do?

Don't touch Issue/Merge Request when importing GitHub comments as it will trigger an update on updated_at field. It also use updated_at as the last updated date doesn't matter the Issue/Pull Request state.

Why was this MR needed?

After import from GitHub, sorting issues by "last updated" doesn't work as expected.

Does this MR meet the acceptance criteria?

  • CHANGELOG entry added
  • Tests
    • Added for this feature/bug
    • All builds are passing
  • Conform by the style guides
  • Branch has no merge conflicts with master (if you do - rebase it please)
  • Squashed related commits together

What are the relevant issue numbers?

Fixes #21567 (closed)

Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: 21567-fix-sorting-issues-by-last-updated-after-import-from-github