Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Consider removing "Legacy JIRA" from the issue descriptions #123

Closed
vlsi opened this issue Aug 6, 2022 · 4 comments
Closed

Consider removing "Legacy JIRA" from the issue descriptions #123

vlsi opened this issue Aug 6, 2022 · 4 comments

Comments

@vlsi
Copy link

vlsi commented Aug 6, 2022

See https://github.com/mocobeta/forks-migration-test-2/issues/1872#issue-1328214873

Does "Legacy" add much value? I do not think so.
Something like "Migrated from LUCENE-1879" would probably be better
@mocobeta
Copy link
Contributor

mocobeta commented Aug 6, 2022

Relates to #122 - @mikemccand do you have thoughts on it?

@mikemccand
Copy link
Member

Just repeating what I said on #122

I'm OK with shortening it somehow if we can, but I think the sentiment must remain -- we need to convey this was a migrated comment to future people who didn't even know we did this issue migration. Maybe "Prior Jira: "? "Migrated Jira: "? "Old Jira"?

We could remove the by prefix after the : at least?

@mocobeta mocobeta mentioned this issue Aug 6, 2022
Merged
@mocobeta
Copy link
Contributor

mocobeta commented Aug 6, 2022

Addressed in #128.

@mocobeta
Copy link
Contributor

mocobeta commented Aug 6, 2022

#128 was merged - I'm closing this. Thanks @vlsi and @mikemccand for your suggestions.

@mocobeta mocobeta closed this as completed Aug 6, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@vlsi @mikemccand @mocobeta