古い割り当てクエリ

データとレポート
,
1

トピックの割り当てを開始すると、必然的に古い割り当てが発生します。

それらを見つけることにしました。

したがって、他の人が役立つ場合に備えて、クエリを以下に示します。
カスタマイズするサブクエリが2つあります。

  • SonarSourcers（なぜ「スタッフ」を使用しなかったのか私に尋ねないでください）
  • teams
-- 目標: 古い割り当てを表示する
--    割り当てから7日間経過し、
--    SonarSourcersからの公開アクティビティ/「通常の」投稿がない場合
--    およびSonarSourcerの投稿が最後の投稿ではない場合


WITH

-- すべての割り当て済みトピックを検索
assigned_topics AS (
    SELECT a.topic_id
        , assigned_to_type
        , assigned_to_id
    FROM assignments a
    JOIN topics t ON a.topic_id = t.id
    JOIN posts p on p.topic_id = t.id
    LEFT JOIN post_custom_fields pcf ON pcf.post_id=p.id AND pcf.name='is_accepted_answer'
    WHERE active = true
        AND a.updated_at < current_date - INTEGER '7'
        AND t.closed = false
        AND pcf.id IS NULL
--        AND a.updated_at > '2022-01-01'
    ORDER BY t.updated_at desc
),

-- 各割り当て済みトピックで、最後の割り当てを検索（複数存在する場合があります）
last_assignment AS (
    SELECT max(p.post_number) AS assignment_post, p.topic_id, max(p.created_at) as d
    FROM posts p
    JOIN assigned_topics ON p.topic_id=assigned_topics.topic_id
    WHERE p.action_code in ('assigned', 'assigned_group', 'assigned_group_to_post', 'assigned_to_post')
    GROUP BY p.topic_id, p.created_at
),

-- その会社で働くユーザーを検索
SonarSourcers AS (
    SELECT u.id AS user_id
    FROM groups g
    INNER JOIN group_users gu ON g.id=gu.group_id
    INNER JOIN users u ON u.id = gu.user_id
    WHERE g.name='sonarsourcers'
),

-- 各人のプライマリチームを検索
teams AS (
    SELECT distinct on (user_id) -- 一部のユーザーは2つのグループを持っています。1つに絞り込みます（任意）
        ss.user_id, g.id as group_id
    FROM SonarSourcers ss
    JOIN group_users gu on gu.user_id=ss.user_id
    JOIN groups g on g.id = gu.group_id
    WHERE -- 一部の重複グループを削除
                 g.id not in (10, 11, 12, 13, 14 -- 信頼レベルグループ
                    , 1, 2, 3 -- 組み込みグループ
                    , 41 -- SonarSourcers
                    , 47 -- SonarCloud - 代わりにスコードを使用したい
                    , 53 -- .NET Scanner Guild
                    )
),

-- SonarSourcerからの割り当て済みトピックの最後の投稿を検索
last_staff_post AS (
    SELECT p.id AS post
        , p.topic_id
        , max(p.created_at) AS last_staff_post
        , la.d AS last_assignment_date
    FROM posts p
    JOIN last_assignment la ON p.topic_id=la.topic_id
    JOIN SonarSourcers ss ON ss.user_id=p.user_id
    WHERE post_type = 1 -- 通常
    GROUP BY p.topic_id, p.id,la.d
),

-- トピックの最後の公開投稿を検索
last_post AS (
    SELECT p.topic_id as topic_id, max(p.id) as post_id
    FROM posts p
    JOIN assigned_topics at ON at.topic_id = p.topic_id
    JOIN users u ON p.user_id=u.id
    WHERE post_type = 1 -- 通常
    GROUP BY p.topic_id
),

-- 最後の投稿リストからSonarSourcersの投稿を削除して、
-- 明らかにユーザーを待っているトピックを削除する
last_post_trust_level_limit AS (
    SELECT lp.topic_id
    FROM users u
    JOIN posts p ON u.id=p.user_id
    JOIN last_post lp ON p.id = lp.post_id
    WHERE u.trust_level < 4
),

-- すべてをまとめる
stale_topics AS (
    SELECT lsp.topic_id
        , max(lsp.last_assignment_date) as "割り当て日"
        , max(lsp.last_staff_post) as "最後のスタッフ投稿"
        , CASE WHEN at.assigned_to_type = 'User'  THEN u.id END AS user_id
        , CASE WHEN at.assigned_to_type = 'Group' THEN g.id ELSE teams.group_id END AS group_id
    FROM last_staff_post lsp
    JOIN assigned_topics at ON lsp.topic_id=at.topic_id
    JOIN last_post_trust_level_limit lptll ON lsp.topic_id = lptll.topic_id
    FULL OUTER JOIN users u ON assigned_to_id=u.id
    FULL OUTER JOIN teams on teams.user_id=u.id
    FULL OUTER JOIN groups g ON assigned_to_id=g.id
    WHERE lsp.last_staff_post <= lsp.last_assignment_date + interval '7 days'
    GROUP BY at.assigned_to_id, lsp.topic_id, at.assigned_to_type, u.id, g.id, teams.group_id
)

SELECT count(topic_id), user_id, group_id
FROM stale_topics
GROUP BY user_id, group_id
ORDER BY group_id
「いいね！」 3
2

私たちのモデルでは、チームにメンバー（またはサブチーム）を割り当て、チームにメンバーを割り当てます。

チームの初期トリアージと再割り当ての状況を見てみましょう。

-- goal: find time from assignment to group
--    to re-assignment to sub-team / SonarSourcer
-- [params]
-- date :start_date = 2022-10-01

WITH

-- find last group assignment in the thread
group_assignment AS (
    SELECT max(p.post_number) AS assignment_post, p.topic_id --, max(p.created_at) as d
    FROM posts p
    WHERE p.action_code in ('assigned_group', 'assigned_group_to_post')
        AND p.created_at >= :start_date
    GROUP BY p.topic_id
),

-- get the details of the assignment post
group_assignment_deets AS (
    SELECT p.id as post_id, p.created_at as d, p.topic_id, pcf.value as who
    FROM posts p
    JOIN group_assignment ga on ga.topic_id=p.topic_id
        AND p.post_number = ga.assignment_post
    JOIN post_custom_fields pcf ON pcf.post_id = p.id
    WHERE pcf.name = 'action_code_who'

),

-- find the re-assignment that came after the group assignment
next_assignment AS (
    SELECT min(p.post_number) AS assignment_post, p.topic_id --, min(p.created_at) as d
    FROM posts p
    JOIN group_assignment ga on ga.topic_id=p.topic_id
    WHERE p.action_code in ('assigned', 'assigned_to_post', 'reassigned_group', 'reassigned')
        AND p.post_number > ga.assignment_post
    GROUP BY p.topic_id
),

-- get the details of the assignment post
next_assignment_deets AS (
    SELECT p.id as post_id, p.created_at as d, p.topic_id, pcf.value as who
    FROM posts p
    JOIN next_assignment na ON na.topic_id=p.topic_id
        AND p.post_number = na.assignment_post
    JOIN post_custom_fields pcf ON pcf.post_id = p.id
    WHERE pcf.name = 'action_code_who'
),

-- calculate days to reassignment for each thread
days_per_team AS (
    SELECT gad.who as team
        , extract(epoch from (nad.d - gad.d)/86400) as days
    FROM group_assignment_deets gad
    JOIN next_assignment_deets nad using(topic_id)
)

SELECT
    team as "Team"
    , count(*) as "Thread count"
    , round(avg(days)::numeric,2) as "Avg days to reassignment"
    , round(max(days)::numeric,2) as "Max"
    , round(min(days)::numeric,6) as "Min"
FROM days_per_team
GROUP BY team
ORDER BY "Thread count" desc

このクエリにはカスタマイズする箇所はなく、「そのまま動作する」はずです。

「いいね！」 2