Nir Haimov Community Champion

@Halyna Berezovska Just now i was also managed to accomplish this by using curl command script: - atlas-clean - atlas-package - curl -X POST --user "${BB_AUTH_STRING}" "https://api.bitbucket.org/2.0/repositories/${BITBUCKET_REPO_OWNER}/${BITBUCKET_REPO_SLUG}/downloads" --form files=@"target/$(cd ./target/ && ls -1…

Thank you @Halyna Berezovska Will appreciate if you can keep me posted if the featured approved or not. and if yes, when it's gonna be released :)

Hi @Halyna Berezovska Thank you for your answer! This is the output of the "atlas-package" stage: <span>[INFO] Project POM found</span><span>Executing: /usr/share/atlassian-plugin-sdk-8.0.16/apache-maven-3.5.4/bin/mvn package -gs /usr/share/atlassian-plugin-sdk-8.0.16/apache-maven-3.5.4/conf/settings.xml</span><span>[INFO]…

@Hi @Narendra Kumar I never encountered this issue, so can't tell for sure. Why not just remove the commented and unnecessary code? Or splitting the code as the error message suggest?

Hi @Suhita Athavale Can you please share screenshot of your field and it's available values? Also, i'm guessing you are using some REST API that return you that error. Can you please share your code too?

Hi @sachin.sharma Your code is fine, the problem is in Jira. You just need to add "Epic Link" to the create issue screen in Jira. Te field have to be available in the UI action so you will be able to do it also from the REST API. Let me know if you still encounter problems after adding the field.

Hi @Andy Case I think it's not possible. In email you can use smart values, and few more (as you said) high level roles that had been setup organisation-wide. Smart values are only for the triggered issue, there is no option to select any project field.

Hi @Shradha Singh Atlassian not supporting development in Jira, especially not in Scriptrunner which is a 3rd party plugin. i would suggest you not to update to 8.8.0 just yet, many companies did not updated their plugins to compitable with Jira 8.8.0 (i guess because of the COVID-19) I think 8.5.1 will be a better start,…

Hi @Shradha Singh @Shradha Singh Sorry to tell you, but your code is a complete mess... Tones of unnecessary imports... Here is a working example for Jira 8 to create issue import com.atlassian.jira.bc.issue.IssueService; import com.atlassian.jira.component.ComponentAccessor; import…

Hi @Shradha Singh , First of all, stop write additional "answer" in the post, and write "reply" to the relevant post instead. Second, please explain in words, what are you trying to do exactly step by step? I see a lot of code and big part of it looks not relevant at all...

check the id of your "epic link" field, it might be something else, but API body should be the same concept

Hi @sachin.sharma , First, you have to add "epic link" to the UI create screen, otherwise it will not work via REST API. Once you add it, it your API use this body as example: { "fields": { "project": { "id": "12200" //your project id }, "summary": "Nir API Test", "issuetype": { "id": "10100" //this is the id of "task" },…

Hi, I think this search work by username or userKey, not by email

Hi @sachin.sharma In the issue you are creating, just add another field called"epic link" and set it with the epic you want. Of course "epic link" should also be available in the create screen of the issue via the UI

Thank you @PD Sheehan ! That's exactly what i needed :) 

With pleasure! :) If this case is closed from your point of view. Please mark my respond as the answer by clicking "accept answer" Thanks.

Ohh, i see, That kind of automation not support what you want. you can't do that with this kind of automation. Also, what you want to accomplish is 2 different automations. 1. set "front-end" will not let the user submit his change without setting the relevant team and will popup an error message for him. 2. set "back-end"…

I guess you wanted to attach another image when you said "this one" but there is nothing in your message :) 

it's hard for me to tell without seeing the situation in my own eyes. But the AO queries should be the same for every database, otherwise it will extremely hard to develop plugins to support all databases types. I think you need to figure out how to make sure that MyDataAO[] mydata…

It's pretty weird that you need to change it to "\"NAME\" to work on postgress, i don't remember i had to do it in the past... But ("Name = ?", campo)) will work on MySQL, so you don't need to do another change for MySQL Hope my answer help

are you using the built-in jira automation? this screen?

Hi, Please explain further, what do you mean "getting issues", what issues? what do you mean by different databse? different between where to where? which databases type?

Hi, i don't think it's exist in the database, but anyway, all you have are 3 options, not hard to remember: 2 = To Do 3 = Done 4 = In Progress

Hi, What trigger do you want to use that missing? Can you share screenshot so i will be sure of what automation you are talking about? Thanks.

You Should open ticket support to Atlassian in that case

@Adrian Stephen These steps are before the upgrade, if i understand right, @Vinay Sharma asks for post upgrade tests

Hi @Vinay Sharma My suggestion, is to test first the basic functionalities: * Login * Create issue * Edit issue * Transition issue * Close/Resolve issue * Delete issue * Make sure email notifications of all the above actions being sent. These are the basic things you want to make sure works so the regular users will be…

Hi, Try using "gh.plan.sprint.actions" or "sprint-move-actions" it till add you button in the 3 dots menu, there is no location (i think) for button near the "green" "blue" "gray" colors

Hi @Fai Chan So where are you stuck now? Did you get the Jira license but can't go back to your JIra to put it?

still check for this specific permission. You can be the sire admin, and be the person with most access in JIra. Still, if in the project permissions scheme you don't have this permissions you will not see the dev section. Note, Project permissions are stronger than anything else. You can be Jira admin and have access to…