Alex Koxaras -Relational- Community Champion

@Jessresolution must only be set when the issue is in the final status (e.g. completed, canceled, done, rejected, etc). There is not point and is clearly wrong to add the resolution when you first create an issue. This is what is messing you charts in the first place. Created vs Resolved chart will show you exactly what is…

Please post here your API command, as well as the issue create screen.

Hi @Jess First thing's first: Issues that are not even in the "Done" status category show up as Resolved. This is due to the fact that resolution is not cleared when issues are reopened (via workflow post functions) Resolutions can be set (and are global variables) via jira settings (cog > issues > resolutions). If you are…

And also, paste a screenshot of an issue, to see all the available fields please.

Can you use the "Find your field" and paste the results here? (open an issue, click the ellipsis menu, and then "find your field". Type "story points" and hit enter)

Hi @Pele Tauvela I'm not quite sure what columns you are trying to rename. Can you please provide certain screenshots, or try to explain a bit further of what you want to achieve? Alex

Yes, you might work with python, but "screens" is a Jira essential feature. When you create an issue/ticket on Jira, a popup screen appears, which prompt you to complete certain fields (mandatory and optional). Screens can also be used on workflow transitions. Screens are also used when a user creates, view or edit an…

Hmmm...I'm getting correct results: The only difference I see is that I have checked the box "send message as automation user". Try adding this and try again.

Then see if the assignee field is present on that issue type create screen. If not, add it on the screen.

@Elisabeth Hunt in that field write the name of the organization and THEN click ADD :)

Hi @Elisabeth Hunt No, even in trial version you may have multiple organizations. You don't have any access of adding an organization like the image below?

Hi @Joe Osborne Did you take a look at these examples? https://developer.atlassian.com/server/jira/platform/jira-rest-api-examples/ If assignee is a mandatory field, then you have to include it in your API. Let me know if the above helps. Alex

@Elisabeth Huntif my answer suit your needs, kindly mark it as accepted, to help other members in this community. Thanx! :)

* In the lookup component, use the filter= "weekly planning". * Add a advance condition, as @Bill Sheboy stated with {{lookupIssues.size|0}} is greater than 0 * On the Send Slack component write something like: Hey team - we've got the following issues left in this sprint:{{#lookupIssues}}* {{key}}{{/}} Test the rule again

Glad to help you out!

Hi @Alex Tartakovsky "Issues" on a project is now a feature which you can activate if you go to project settings > features (turn it on). If you have the bulk change global permission you can: * Go to advanced issue search * Search for all issues of THAT project * Click the Bulk Change option Let me know if that was what…

Hi @Lauren Hall By default, when creating a project which has a BUG issue type, Jira creates a separate screen for that issue type. E.g. So what I would do: * Click on the "Screen" on the BUG Row (in my example that would be HWA: Kanban Bug Screen) * On the tab that would open, I would again click on the available screen *…

Hi @Elisabeth Hunt and welcome! Automation has a rule library, and it comes with a template for what you want: You just have to modify it a bit, adding some Ifs etc: I really hope that these 1200 will have some common agents to attend to their issues. Keep in mind that you can only add 65 components inside a rule. Let me…

With my experience, this field is something that should be up-to-date any time someone opens an issue to view it. If estimates are updated once a day, then yes, once-per-day is something that I could live with it. But if you have multiple projects, with multiple teams, this possible wouldn't work. REST API would be…

The rule you have created will run only for the issues that have changed since the last time that rule executed. What I would do, for testing purposes, is to: * Change the trigger to manual * Remove the "only include issues that....", just to make sure that I will receive results * Run manually the rule * See if I receive…

Click Products on the header menu.

Hi @Pedro Hernandes Filter subscription currently works for individual users and groups. You could use most likely an automation, with webhook to send results to a slack channel. This automation would use a scheduled trigger, to manage the weekly sent. Let me know if that helps. Alex

Hi @[deleted] Sandbox is located via the admin section: * Go to cog > user management * Click product on the header menu * Click sandbox on the left panel Hope that helps Alex

@Olivier Molliesit would really help if you could be more precise on what you wanted to achieve. But if I guessed correctly, you would edit that issue (as an action) and then use the advanced section to edit the field, based on this documentation https://docs.automationforjira.com/smart-fields/advanced-fields.html

Everything has pros and cons. Using a template is faster and easier (that's reason of having a template after all). However, a template could have fields and statuses which you will not use. Less fields and statuses will confuse less your colleagues. A custom solution will take more time to implement and will need to be…

Also read this https://support.atlassian.com/jira-service-management-cloud/docs/what-are-the-project-templates/

I don't know about any document. However, I would suggest to * Start a conversation with all stakeholders (finance team) * Gather all requirements and business rules (SLAs etc) * Design the solution for your JSM project * Implement it * Test it * Go live with it You could enrich it by adding incoming mail handlers, so as…

@Jack BrickeyI confirm that what Olivier says is true. I can't see also the field I've created. However if you try the advance issue condition, then it works like a charm.

@Olivier MolliesI said "advanced issue condition" and not "issue field condition" :)

@Garg, Prateekclick "view workflow" on each of these issues, and paste the screenshots please.