Hernan Halabi Community Champion

I wouldn't be surprised that those are created by default when you create a new project using one of Jira project templates. Delete them, create projects and check again. I believe we had this on one of the instances our team managed. The solution if so: create projects based on existing projects rather than Jira templates

If you are on cloud you should be able to do it from here 

Sounds like you are trying to use your workflow for some issue types and the scrum one for others. You must assign each of them on the workflow scheme. You can use one workflow on multiple issue types but issue types can have a single workflow assigned to it. Is this what you need?

Make sure that your company users are in a role within your JSD project and give that role browse project and add comments on the permission scheme

You can always create the workflow that fits your needs, apply it to existing projects and the share it to new projects you create using one of those projects as a template

If you are the jira administrator then you can. You must import a new csv that contains that information along the ticket IDs of the current tickets and the ticket summary, in theory you don't need anything else, in my experience add the issue type and ticket status as well. When doing a new import to update existing…

have you checked that the issues have a resolution? it's important that it's the case. Jira considers issues as closed based on the fact that the ticket has a resolution not the ticket status.

Never had to but seems that you can https://community.eazybi.com/t/how-to-create-the-cumulative-ratio/2060/2

I believe that the feature is missing from the customer portal. What you are trying to use was originally meant for jira core and software solutions

Not free but cheaper than an agent license in the long term if you plan to do this for many customers

Agree, you seem to be showing the post function from the outgoing transition based on the behavior described. Please share both so we can better help you

Try to avoid it because of the security of the environment since permissions will get more complex if so. I would consider adding EazyBI and send some pretty reports by mail. Not sure if you can automate it though

I believe it's because the tickets url are not the ones from jira portal and therefore they don't have access to it, they should be licensed users in order to see the output of the filter or make the project itself available without any users license which I wouldn't recommend due to security concerns

From The history tab we can see that the resolution is set but afterwards you have a poat function that changes it to done. You need to edit the workflow and remove the post function

Sounds like you have a few options available, you can either open the XML file and search within it for that issue or report this back to Atlassian and they might be able to see that on the database from your cloud instance and fix it before you export the information. Second option should be the less painful

Hello @Audrey Bay , could you send a couple of print screens so I can review in more detail what you're saying. It would be good to have a print screen from the history tab of one of those tickets

Do they actually have a resolution? it doesn't matter if the status is done, what's important is that the subtask have a resolution value assigned. If they do, then they should have a strike-trough if you open the parent ticket.

If the suggested gadget isn't enough and you have some budget. Consider adding EazyBI, it shouldn't be to hard to make that report on it and is very useful when jira reporting capabilities aren't enough

I'm not sure what is the question. You need help to understand how to make the workflow transitions? Describe the expected result since it might help to understand better the requirement

hi @Amna Ali were you able to figure this out based on the input?

To do so you must map your workflow to a the workflow scheme that the project is using, and associate that one to the bug issue type. In a similar way, you must do the same with the screen. It must be associated with a screen scheme which you later will assign to a issue type screen scheme. The last one is the one that you…

Hi @فادي did this help you solve your issue? do you need any extra assistance? would be good to mark this as solved if it's really the case

Hi @Eric B_ were help you solve your issue? do you need any extra assistance? would be good to mark this as solved if it's really the case

Hi @Eugenia Peralta did this help you solve your issue? do you need any extra assistance? would be good to mark this as solved if it's really the case

@Annie was your issue solved? 

Emails are sent within a minute or two. You can't disable the merge of the emails. If it's going to happen almost right away, I would consider making the text considering the fact that most likely both emails will arrive together, something like "Quick update your issue has been acknowledged by and we should be working on…

looks like you created a new ticket and right away you moved the issue to acknowledged so Jira merged both notifications into one email. Give it some time to receive the ticket created notification and then move it to acknowledge and show me the results if that didn't work

You need to use the automation module from JSD to create rules when you move your ticket to certain status trigger a different email notification to them

Great,glad to help 

Agile boards are based on queries, usually are for one project but you can do a query for all projects and see that output as an agile board. See on the board settings that you have a query there that you could change for another or edit that one