Hana Kučerová Community Champion

Hi @anneliese.kalwy , hopefully I understand it right... I would do something like: WHEN: Issue transitioned from To Do to In Progress IF: Issue Type equals Story For Parent: - if "date field" is EMPTY - update "date field" to now

Hi @CAMPAGNOLE Philippe , welcome to the Atlassian community! Would you please share the groovy script here? What kind of array are you trying to delete? Thank you.

Indeed, that is really strange. If you set the Resolution during the transition, it should not be empty. To be honest - I'm out of ideas, what else to try. Maybe just one another check - did you publish the workflow after all the changes?

Hi @Beverly Braham-Durica , two questions please: 1) what is the definition of closed issue in your case? Issue is in specific status or has resolution set or ??? 2) if issue is closed, which value should be in the field? 0? Thank you.

You can also add some comment with the rule, so that you DEV team get the information, that issue has been closed automatically based on the linked issue closure or something like this.

Question 1: I just wanted to say, that it seems to me there could still be situations, where you need to close the issue in JSM project (for example based on the information from reporter). so blocking this action doesn't seem right. Question 2: Yes, I would create the second rule and close the linked issue in JSW.…

Hi @serge calderara , It doesn't feel right to block the close transition - it seems to me your N1 can get information by the reporter, that they can close it (or can by closed by reporter) in JSM. Then the appropriate action should happen in the JSW project. I would create bidirectional automation rule, which will close…

Please check, if you set the post functions to the correct workflow and transitions. I strongly believe this should work. If you look to the history of the issue, you've transitioned, are you able to see any useful information connected with resolution?

I would recommend you to try to remove the resolution field from the screen. If you are setting the resolution using post function (everytime you transition the issue to status Resolved), it should be ok.

Hi @Brant Schroeder , it looks like there are a lot of new challenges for "beginners". I've achieved "First answerer" today and I can see others like "Planting the seed", "First Post", "Group Post" in next challenges list.

Hi @Ramondrio Imanuel , I apologize, but I don't understand. Would you please provide me more information, what you are trying to achieve?

Thank you. I can see there's screen on the transition: "JIRA Service Desk Resolve Issue Screen - 7" - is there the Resolution field on this screen?

Would you please also add the column Resolution to the view? In general it should work like this: When you transition issue and during the transition you set the Resolution field (for example to Done), Resolved field (date) is also set (and vice versa - if the Resolution field is cleared during the transition, Resolved…

Hi @Novakopa , welcome to the Atlassian Community! Do I understand it correctly, that after the issue transition to "done" status, Resolution field is empty and the issue looks like it is still unresolved? The first thing I would recommend you is to navigate to the workflow and check the appropriate transition, if…

Hi @Keerthana P , you can use Jira automation functionality for this scenario - create automation rule, which will react on issue creation in JSM project and which creates copy of the issue in JSW project.

Hi @John Hill , welcome to the Atlassian Community! You can find more about tokens here. There are a lot of things happening with Insight now, so I'm not sure, if this API documentation will be valid in the future, but I think you've got the correct documentation now.

Hi @Ramondrio Imanuel , try to add "as Map" like this: import groovy.json.JsonSlurper String requestBody = '{ "name": "John", "ID" : "1"}' JsonSlurper jsonSlurper = new JsonSlurper() Map object = jsonSlurper.parseText(requestBody) as Map object.name

I've just tested it with manual trigger and it works for me. Hopefully image of the audit log would help us determine, what's going on.

Yes, but it is a little bit tricky to find it out. It is for example visible in the URL, when you click on the release name and view the release detail. URL should look like: https://your-site.atlassian.net/projects/KEY/versions/10000/tab/release-report-all-issues 10000 = release id

To be honest I don't know what else to try. It works for me, so it looks like some sort of bug :-(

Hi @Kántor Tibor , I was able to reproduce this behavior as well with JQL: assignee changed In Jira I get many issues, in Confluence I get only one issue (and even incorrect one!) There's been a lot of issues with this functionality. You can try to debug it more and find out, which search query is used, but I think usage…

Hi @Levi Orlando , welcome to the Atlassian Community! We were communicating about this with Atlassian's support yesterday. To have all users as objects in Insight schema, you need to export all users from user directory and import them using CSV, where you will reference "Jira User" attribute with ID from the database.…

Hi @[deleted] , please, why do you need such a thing? To be able to create new version of the content, something must be changed, either content or title...

Thank you. Actually it looks good, I believe this should work. I will test it using my instance and let you know. Maybe we will need to use additional fields...

Hi @Áron , would you please share us screenshot with the configuration of Edit issue fields action detail? Thank you!

Hi @sandip , welcome to the Atlassian Community! I believe the reason you're not able to find anything is the next-gen projects were not designed for such purposes. I think it would also help, if you define, which functionalities you expect you have available, how does you process looks like etc. Maybe you don't need any…

Hi @Lukas Germerott , welcome to the Atlassian Community! To be honest, I can't imagine doing it other way then switch to the classic project. Then you will be able to add a screen to the transition.

Hi @Hamid , have you saved the settings? Please try to also add some text to the footer and save it to be able to find it on the page.

Hi @Hamid , in the space settings navigate to the: "Look and Feel" -> "Header and footer" and type type four dashes in a row in the field Footer:

One more thing - you can use release id instead of name, something like: fixVersion = 10000 Then it doesn't matter, how the release is named and you can change it anytime, but is not clear from the JQL at the first sight, which release are you referring to.