1. Fidel Castro Armario Avatar Fidel Castro Armario
  2. Untitled project
  3. JIRA Workflow Toolbox
  4. Issues

Problem with "Copy a parsed text..."

Issue #168 resolved
Astrid Harms created an issue

Hello all,

in our workflows we use the post function "Copy a parsed text to a field" - which is working fine. Additional we use another Plugin "Exocet" to synchronize the issues between two projects. Until now, everything worked good, the "Copy a parsed..." copied the issue key in a field and via Exocet this value was synced to the linked issue. Now we are testing a new Exocet version and the sync of this field is not working anymore.

Exocet told us, that they can't guarantee the cooperation with other Plugins (I understand this). But since it has worked previously, I want to ask you, if you have any idea of the reasons.

Thank you very much and kind regards Astrid Harms

Comments (14)

  1. Fidel Castro Armario repo owner

    Hi Astrid,

    Can you please describe the problem? The problem is only in the synchronization of linked issues, or is also failing current issue's field setting?

    Have you tried the most recent version of JIRA Workflow Toolbox (currently 2.1.34)?

    Have you checked JIRA log file for error messages?

    Fidel

  2. Astrid Harms reporter

    Hi Fidel,

    thank you for your fast answer!!

    I will try again ;o) The problem is, that the field, which is filled via JIRA Workflow Toolbox, is not synchronized. The setting of the field works.

    We are using 2.1.23. We are just upgrading our Plugins and we started with Exocet & there we have the first showstopper... ;o( If you see a chance, that the problem will not exist in 2.1.34, we can try it.

    We didn't check the log files right now. I will ask my technical collegues.

    Kind regards Astrid

  3. Fidel Castro Armario repo owner

    I don't know how Exocet works. I don't think version 2.1.34 will solve the problem, since no changes have been made in the way custom fields are set. Anyway I recommend you to update because new version provide many improvements, new features and bug fixes to your current version.

    One question: Which field are you setting? Is a custom field? Which type is it?

    Can you attach a screenshot of post-function's tab of your transition configuration?

    Fidel

  5. Astrid Harms reporter

    Hello Fidel,

    thank you very much for your help!

    Yes, the field called "externe ID" is a custom (text)-field.

    I will try to explain our concept - shortly ;o) We've got two projects: One project is the "external / customer" view for the correspondence with the customers. One project is the internal view with (additional) internal information. Each issue in the external project has got a duplicate and linked issue in the internal project (and vice versa). Via this link Exocet is synchronising all field values between the projects. So, we've got only "one" project to work on & we can seperate external and internal view.

    Not every collegue can browse the external project. But if he talks to a customer about an issue he should know the key in the customer's project. And that's why we've got the field "externe ID", which displays the issue key of the linked issue in the internal project.

    Perhaps, it seems to be a little complicate but it's a good way to work only in one project.

    I've added you a screenshot of the workflow transition, when the toolbox parses the issue key to the field. Then the field is filled with the issue key & via the Exocet sync it was synced into the linked issue. And that is not working anymore. (Before this transition, the workflow of the corresponding project Exocet duplicates the issue after creating.)

    The create and link-function is on both sides: When we create an issue in the internal project and when the customer creates an issue in the external project. If the customer creates an issue the post functions are a little bit different, but they're still working...

    Please excuse, if I ask you too much ;o) I'm afraid, it is not so simple... But before upgrading to Exocet 2.4.0 it worked. After upgrading the value is set by the toolbox, but the sync via Exocet starts not.

    Best regards from Germany Astrid

  9. Astrid Harms reporter

    Dear Fidel,

    you are so helpful! I like that, thank you! :o) I know the function & we're using it in some transitions - when we use transition screens, Exocet is not working reliable.

    We can use it here, too, of course. But... 1. We have to change all affected workflows (only a little bit of work, doesn't matter). 2. I would like to know why it does not work anymore... Where is the fault?

    But that's not your job - perhaps Exocet will help.

    Thanks again! Cheers Astrid

  10. Fidel Castro Armario repo owner

    Hi Astrid, as I told you, I don't know how Exocet works, but I think it should work with JIRA Workflow Toolbox post-functions, since this plugin uses official JIRA API for writing into custom fields.

    Indeed, Exocet previously supported the plugin, and now it doesn't. If you contact Exocet team for more information, you can tell them to contact me if they need my collaboration to solve the problem.

    BTW, I suppose the same problem should be happening with other plugins that provide post-functions for setting custom fields, since all of them use the same API for doing it.

    Fidel

  11. Astrid Harms reporter

    Hi Fidel,

    meanwhile I tested the post-function "Write field..." and it's not working as well. That surprises me really! I am in contact with the Exocet team and I will tell them to contact you (thank you for your offer!).

    Best regards Astrid

  15. Log in to comment
Assignee
–
Type
enhancement
Priority
major
Status
resolved
Version
2.1.23
Votes
0
Watchers
2
Jira: the preferred issue tracker for Bitbucket. Join the team!