Why am I unable to change the priority of a ticket that has already been created?

[Felicia Moser]

We currently have boards up and running. We were going through our backlog items and could not change the priority of tickets previously made. We have a test JIRA board and and we are able to change the priority arrows there. I'm new to JIRA/didn't set up our boards. What can I do to make it so that we are able to change the priorities of the ticket at any time during the sprint? 

[whootang12 · Accepted solution]

I spoke with Atlassian on this, there is no way to do this. They added this as a feature request.

[Srinivasa Pidathala]

Hello @whootang12 ,

Could you please share the Feature request link here that would be helpful.

Thank you!

Best Regards,

Srinivasa

[Norman Abramovitz]

You need to stash your changes and get back to the state when you made the commit. Then you can use the commit amend to update the message.

http://blog.jacius.info/2008/6/22/git-tip-fix-a-mistake-in-a-previous-commit/

[Abdulrazaq Mohammed Ali Omar]

if your commit was the most recent commit then you can use:

git commit --amend -m "New commit message"

and put the correct commit message and Sync your BitBucket account with JIRA, and it will point to the correct JIRA issue after that, you can also use:

git rebase --interactive $parent_of_flawed_commit

If you want to fix several flawed commits, pass the parent of the oldest one of them.

[whootang12]

Sorry, I don't think I made my original question clear:

1. Make my change to the file

2. git add .

3. git commit -m "EZGC-15 issue is fixed"

4. git push

Now, I realize I should have made it "EZGC-14 issue is fixed", how do i update? The command you mentioned requires a merge and then a 2nd commit. If I'm not mistaken, the only time I will see the linked commit in JIRA is after I've pushed my changes, and thus that is the time I'm most likely to find my mistake. You are right that I can amend my message before pushing, but that doesn't help much.