Tuncay Senturk _Snapbytes_ Community Champion

Hi @oskfel_po You're absolutely right. Atlassian's focus is more on project- or issue-level permissions. Proforma allows you to define who (based on their roles, groups, or the issue type) can see or interact with specific forms. You can configure a form so that regular users might be able to see issues or forms but won’t…

Hi @oskfel_po Page level access restriction isn't a built-in feature for project-specific pages like forms, goals, or summary pages. Instead, the access is given at the project permission level. You may want to check out ProForma Forms for Jira app.

Did you try to run it? Sometimes the editor shows compile errors but it may run ok.

I never had an RC car as a kid! But I made up for lost time by buying plenty of RC cars and trains (Thomas the Tank Engine and friends)—for my son (or for me 😄). We’ve raced, crashed, and rebuilt so many times that I’m pretty sure I had more fun than him. Killing two birds with one stone—father-son bonding and living my…

Hi @Jakub Gawinkowski In the context of ScriptRunner, you use issue directly, you don't need to define it. remove this definition Issue issue and use something like below def customFieldManager = ComponentAccessor.getCustomFieldManager() def tacticField = customFieldManager.getCustomFieldObjectByName("Hyp. Mitre Tactics")…

Hi @Scott Feger The error states that the token being used to authenticate with the Jira/Zephyr API is either invalid or improperly formatted. Jira Cloud API tokens must be generated for the user account under Account Settings > API Tokens. Have you completed this process?

Hi @Gerrit Wahlers In order to see the status of an the request linked through a web link, you need to ensure that the user has the necessary permissions to view the linked request in the external JSM project. The user needs to be added as a participant or be the reporter for the external service request. Other than that,…

No problem! I'm glad it worked!

Hi @Amine Nait Lechguer In the Jira Forge Global Page documentation, it states, "You can only specify `pages` or `sections`, but not both." However, in your manifest, I see the pages listed under sections. Could this be the problem? Please bear in mind that the Atlassian Developer Community is a better place to ask this…

Hi @Mo The create REST method (POST /rest/api/3/issue) already returns the issue ID / key. I do not understand why there is a need to make the second call to retrieve them.

Hi @Bill Sheboy Thanks for asking, actually it depends on Atlassian's policy. If the Forge platform remains free, it will continue to be free. However, if their strategy changes, we may need to adjust our approach to cover the costs.

Hi @Arpan Banerjee As @Bill Sheboy mentioned, you can achieve a basic structure using the built-in Round Robin feature in Automation. However, if you're open to using an app, I recommend trying out SnapAssign, a free app available on the Marketplace. SnapAssign offers several advanced features, including shift support,…

which Jira version are you using? and can you confirm that this is Jira Datacenter?

It makes sense. I'm glad it helped you think in the right direction. 

Hi @Erik Schumann I am not 100% sure but in regular expression (?m) enables multiline mode so it is worth trying the below one. issueFunction in issueFieldMatch("filter = 'filter name'", customfield_12345, "(?m)^DEF.*")

Hi @Dani Campbell Are you sure you are not getting any errors? I don't know Zephyr but I can try to help you with the script. I don't think either Issue.count or Issues.count will wok as they are not Groovy valid syntax. You can use SearchService to search by JQL. I assume hasTestCoverage is valid in Zephyr, and below is…

Hi @Aviraj Roy You can use Issue Statistics gadget. First, create and save a filter that retrieves issues resolved by developers in the last 90 days issuetype = Story AND resolved >= -90d AND "Story Points" IS NOT EMPTY configure the gadget and select the saved filter. However, it will not show the sum of the story points.…

Hi @mbrk Your script looks good, but there is one thing that is worth changing. The makeRequest function returns a Response object (as far as I know), and you need to parse the body (use .json()) to access the roles. Something like the below const getProjectRolesForCurrentUser = await…

I am not sure but it might expect the format to be YYYY-MM-DD, YYYY/MM/DD, DD-MM-YYYY

What type is this custom field? You can find the type on the custom fields page. If it is a date field, it should work properly, but you must include a check for null or empty values.

Hi @Steve Teiv Is your Target End (customfield_121) a Date field? If it's not, the Automation will fail to parse. Null or empty values will also cause the toDate function to fail.

Ok, if it's DC then as far as I recall, in JSM 5.10.x, major components such as the issue create/edit dialogs and form fields began adopting React, and then most select components transitioned fully to React by JSM 5.12.x React-based components require a different approach compared to legacy implementations. These…

Hi @Timetoact I see it's Jira Cloud and as far as I know the select2 dropdowns were replaced (widely) with React-based components long ago (around mid 2020), then Atlassian applied the same for Jira datacenter. However, I don't know the exact version of the changes.

Hi @Arti Patil I am not sure if I get it right but I trust the below code will help you def customFieldA = issue.getCustomFieldValue(customFieldManager.getCustomFieldObject("customfield_XXXXX")) def parentIssue = issue.getParentObject() if (customFieldA == "option 1" && parentIssue == null) { return false // "Parent issue…

HI @Sahil Godse The error says that your system is unable to establish a secure connection to the Atlassian Maven repository which is <a href="https://maven.atlassian.com/repository/public" target="_blank" rel="nofollow noopener noreferrer">https://maven.atlassian.com/repository/public</a> due to a certificate validation…

Ah, I see! As far as I know, the Jira REST API does not allow you to attach a file at the same time as creating an issue in a single request. You have to do this in two sequential API calls.

Yeah, it might be the case. Did you try adding some logs to see how it behaves with data in and out? something like : try: print("Headers:", request.headers) print("Body:", request.data.decode('utf-8')) print("JSON:", request.get_json()) return "Request received successfully", 200 except Exception as e: print("Error…

Sorry, I don't know if there is.

Hi @SGC Associates Ltd I assume you are using Automation's Send Web Request. Since your Flask server works fine with curl, Postman, and even via browsing, you've ruled out the firewall and SSL problems and this is weird. I think you already checked the headers (content-type: application/json, etc) and the json body is…

Hi @tonynasrr As far as I know, they are still part of jira-core and there has been no change. Is there a specific reason you believe there might be a change?