Comments
-
That's a cool way of doing it. Unfortunately, most custom fields only work from the moment they are added to tickets and onward. You might be able to do something against the DB itself through the backend to update it. Or if you have some development skills you could create a script and use JIRA's API to do something. A…
-
When I have to do this I normally sit with the project lead or someone that knows the most about the workflows new and old and have them assist or pre-map the statuses between the two workflows. When you publish the new workflows the program will ask you to map the old statuses to the new ones and then do a bulk update. I…
-
I would also add that to make your life easier to avoid a next time, when setting up the project make a copy of your default permission scheme your company uses and apply it to the new project. I try to keep each project partitioned off from each other as much as possible. You can do this type of partitioning at any time…
-
How did you configure the field? Was it done using a plug-in like Scriptrunner?
-
I've brought it up to the Engineers while I was at Summit last week. I explained the logic behind wanting this functionality, so hopefully we will see something new soon.
-
You're going to have to use the jql and have it include something along the lines of: assignee was Peter and assignee changed during (date1,date2) The date range isn't a great solution, but it's the first step on how I'd tackle it.
