<commit_before># Managing Issues

## Changing Statuses

Status changes are applied by using the `move` command. Most trackers use the basic workflow, allowing you to apply status changes however you like.

However, for more complex systems (currently JIRA), Qissues will conform to the defined project workflows. Upon moving an issue, it will prompt you, if necessary, for any required fields. Similar to creating an issue, you can use alternate input strategies if desired, or it will default to editing a YAML file.

Currently, we will only prompt for required fields, but later we may show all of them, marking them as optional.

Examples:

    # Mark as In Progress
    qissues move 99 progress

    # Mark as Resolved (will prompt for Resolution)
    qissues move 99 resolved

Basic issue trackers won't prompt for additional information, and will never block illegal status changes.

## Changing Assignees

All of the trackers support assigning issues to users.

    qissues assign 99 username<commit_msg>assignment / comment notes<commit_after># Managing Issues

## Changing Statuses

Status changes are applied by using the `move` command. Most trackers use the basic workflow, allowing you to apply status changes however you like.

However, for more complex systems (currently JIRA), Qissues will conform to the defined project workflows. Upon moving an issue, it will prompt you, if necessary, for any required fields. Similar to creating an issue, you can use alternate input strategies if desired, or it will default to editing a YAML file.

Currently, we will only prompt for required fields, but later we may show all of them, marking them as optional.

Examples:

    # Mark as In Progress
    qissues move 99 progress

    # Mark as Resolved (will prompt for Resolution)
    qissues move 99 resolved

Basic issue trackers won't prompt for additional information, and will never block illegal status changes.

## Changing Assignees

All of the trackers support assigning issues to users.

    qissues assign 99 username

There is also a shorthand to assign the issue to yourself:

    qissues assign 99 --me

## Commenting

All management commands also accept an option comment. You can specify one with `-m "your message"`, or you can specify an alterate option strategy instead:

    echo "This is my comment" | qissues assign 99 adrian --comment-strategy=stdin
{'fraction_non_alphanumeric': 0.04077343421605717, 'fraction_numerical': 0.006725514922236234, 'mean_word_length': 4.151515151515151, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '1733828', 'n_tokens_mistral': 605, 'n_tokens_neox': 551, 'n_words': 352}