- fix problem when not expected proeprty is included
- fix data fileds not being copied

This changes any mention of gitlab-ce to gitlab-foss, and any mention of
gitlab-ee to just gitlab.

- move issue trackers properties to
a separated table
- keep backwards compatibily and still be able to read
from properties

Applies to issues_url and new_issue_url

- handling properties needs to be skipped when
creating test records in order to test the legacy
data

- instead of using properties
- backward compatibility has to be kept for now

# Conflicts:
#	locale/gitlab.pot

- instead of using properties
- backward compatibility has to be kept for now

https://community.atlassian.com/t5/Jira-questions/Is-it-quot-JIRA-quot-or-quot-Jira-quot/qaq-p/681163Signed-off-by: Takuya Noguchi <takninnovationresearch@gmail.com>

Adds `# frozen_string_literal: true` to spec/models ruby files

Port of a community contribution from @glensc to upstream.

See https://gitlab.com/gitlab-org/gitlab-ce/issues/47677 for more information

Signed-off-by: Rémy Coutable <remy@rymai.me>

Due to the change in
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/14583/diffs we
can't use the same method to access assets in a CI and the local test
environment anymore.

the ci status icons are generated client side, wo we don't need the
static files anymore.

Due to the change in
https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/14583/diffs we
can't use the same method to access assets in a CI and the local test
environment anymore.

the ci status icons are generated client side, wo we don't need the
static files anymore.

Leaving a trailing slash in the context option causes the jira-ruby
gem to add an extra slash in HTTP requests to the URL, preventing
JIRA from working properly.

Closes #42494

Signed-off-by: Rémy Coutable <remy@rymai.me>

Remove superfluous lib: true, type: redis, service: true, models: true, services: true, no_db: true, api: true
Signed-off-by: Rémy Coutable <remy@rymai.me>

Signed-off-by: Rémy Coutable <remy@rymai.me>