Hi Nic, I am on my way to update the functions that were using the old 10001 to new id but I am getting this error
|Key starts with 'jira.' but is not known to JIRA.|
here is the xml of the workflow and the old Id to be replaced
and here is when I add another jira.status.id
please help thanks
You're looking at unrelated things.
Properties on transitions and status are not related to the resolution id. Additionally, you appear to be trying to set a status property, not a resolution one.
Could you explain what you are trying to do, and what problem you are trying to fix?
Hi @Nic Brough [Adaptavist] , the problem is I want to export my test project using your product which is the Project Configurator, and whenever I am exporting my project on test prod, it says that there is no Resolution Id 10001, I think we accidentally delete that so I came up with your solution to replace all old 10001 with the new Id that's why I'm doing that part.
You are mixing up status and resolution, and your "search and replace" could easily have damaged all sorts of things.
I think you should go back to the backup you took before doing any of this work.
Then describe what you are trying to do and why and we can guide you on how to do it the right way.
Hi @Nic Brough [Adaptavist] , here is the error on the project. I am trying to export this test project from test-prod and import it on prod to see if we can catch the following configs using scriptrunner: Listeners, Scripted Fields, Behaviors , and the JIRA configs : Screens, Custom Fields, Workflow. But this error is preventing us to export the project
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs