투표 플러그인 요구 사항

기여 기능
1

Hey there,

We are looking to use the voting plugin (already installed and in action) for our new feature requests process.

We will set thresholds of votes and time to move feature requests towards being shown to our product team. For example, if the request gets 30 votes in 3 months it will be considered a “Good suggestion” and if it then reaches 70 votes in 6 months it will be a “Hot suggestion” and then be presented to our product team in our quarterly VOC meetings.

We want to be able to show which topics have reached these milestones by using a tag. We want to know if this is something we can automate?

The complete list of requirements we are looking for is:

  • Automatically tag new feature request topics (wouldn’t be linked to votes rather the fact it is new)
  • Automatically tag topics after they reach x votes within x time
  • Automatically close feature requests topics after x time if they don’t have x votes
  • Is it possible to also add a note on the closure?
  • Automatically move closed topics to subcategories

Anyone know what is possible given it’s a plugin and not within the main discourse features?

Thanks!

4개의 좋아요
9

Julia님,

이 문제를 Contribute > Feature 카테고리로 이동시켰다는 것을 알려드립니다. 이 문제는 Voting 플러그인에 직접 적용하기보다는 다른 플러그인으로 처리할 수 있으므로, 내부적으로 가장 좋은 해결책을 논의하고 있습니다: Discourse Automation. 해당 자동화 스크립트 생성을 도와드릴 예정이며, Business 플랜에 자동화 플러그인을 추가하고 있으므로 곧 고객님의 사이트에서 사용할 수 있게 될 것입니다. 플러그인과 스크립트에 아직 많은 작업이 남아 있어 시간이 좀 걸릴 것으로 보입니다. 진행 상황은 이 토픽을 통해 계속 업데이트해 드리겠습니다.

4개의 좋아요
Questions about Automation
11

Thanks @osioke for prioritizing this. In order that we can plan for the eventual use of this feature, could you share a vague timeline for when you think it could be ready for us to use?

1개의 좋아요
14

It is end of the year, so there is a lot of OOO going around. Can we circle back in January? Either it will be done by then or I’ll have more info for you.