Skip to content
This repository has been archived by the owner on Apr 8, 2019. It is now read-only.

Disable issue modifications #6

Open
ghost opened this issue Sep 7, 2015 · 3 comments
Open

Disable issue modifications #6

ghost opened this issue Sep 7, 2015 · 3 comments

Comments

@ghost
Copy link

ghost commented Sep 7, 2015

Some sort of comment tag (similar to MEQS system) that will cause the Bot to not modify the ticket.

@ghost ghost added the enhancement label Sep 7, 2015
@ghost
Copy link
Author

ghost commented Sep 7, 2015

I'd use the IssuePool for that. When it would normally add something to the @issues and @updated_issues variables, check the issue for that comment first and don't add it if one is found.
However, there are two problems with that:

  • Users would be able to post such comments themselves, either by looking at existing comments (if they're public) or by reading the source code.
  • It affects @issue_modules, @crash_modules and @updtd_modules, but not @query_modules as they run the queries themselves. One would have to add that check to every single @query_module. However, currently, there aren't many of them and they don't do anything important.

The best solution is a JIRA customfield, obviously.

@ghost
Copy link
Author

ghost commented Sep 7, 2015

@Mustek said:
Use the confirmation status. Can only be adapted by mods.

@ghost
Copy link
Author

ghost commented Sep 7, 2015

@Tora-B said:
Use confirmation status for what? Arisa does useful things on both confirmed and unconfirmed tickets, though I do think it shouldn't resolve issues that have been marked confirmed, or were just updated by a mod. It's annoying to reopen an issue, only for Arisa to come along and resolve it again.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

0 participants