Hernan Halabi Community Champion

As @Nic Brough -Adaptavist- mentions, you should check the target project rather than the active one. If all is happening in the same project, check the field configuration that is assosiated to the target issue type.

Those might not be showing it there are no users added to such roles. Don't they show up when you try to add a new user to the project? If not, sent a print screen of what you see

Hello @[deleted] check that the project has at least one component created. Once it's there instead of complaining it should allow you to select it and move forward. The other option is to have a field configuration assosiated to the new issue type and mark the component field as optional.

Ok, then if I got this right now, do the following. Edit the workflow scheme of that project and map the new issue types to the same workflow than bugs. You might want to do the same with the issue type screen scheme if you want to see the same fields as well

Hello @A L you can only have different workflows if you have different issue types, each issue type can only have one workflow assosiated to it, what you could do is to have within the same workflow multiple transitions between statuses and each one would have a condition based on the component value. That way you achieve…

Hello @Phil Harman you need to work on your board filters in order to tell Jira to show all issues from the project but those that are action items or decision issue types on the scrum board and then on the kanban show only those. Once that is updated your life should be easier, nevertheless, default issue types are per…

Hello @Arnold Ng I'm pretty sure that we have done this for our customers using service desk SLAs and eazybi. Do you have both or just the second one?

Hello @Bruno Roveri I suggest you start checking some YouTube videos that usually helps more than the documentation. About your questions you have software projects or service desk projects, you can link issues from one with another and users can work on both if needed. Depending on the licenses they have assosiated,the…

Hello @Sam Newman please review that you can see both projects and you have link issues permission on both of them. Also I'm not sure if could be the case but maybe one of the projects is a classic one and another is a next gen. I know they don't work very well together for some things, maybe this is the case as well.

Hello @barronkid I dealt with scenarios like that in the past and you can find in the marketplace apps that can help you sync issues between two instances. That would be the pretty solution. I recall that those weren't an option for some of our customers so in order to avoid the loops we did something like the following.…

Hi Pablo, if I get the idea right. You don't want to allow users to create the same type of tickets from the two places. Assuming that is the case here is what I can tell you. In the portal you can hide certain request types so those can only be created via the create button from Jira itself, meaning that those will only…

Hello @Michael Baguio can you provide more details about the error? What do you have on the logs? Can you replicate the error if you want to?

Unfortunately I'm running out of ideas without being able to play around myself. I'm not sure what are we missing

Let me know how it goes

Hi Jonathan, if reporter is being changed then emails should be working as expected. A workaround I can think is to use issue collectors instead of email. That might work as well

I've done that in the past and nothing got removed, nevertheless I suggest you double check by creating a simple project with a page in confluence linked and do the test on it so you can ensure there is no data loss. You can always do a backup of the space as well

 Not on the computer but yes for mobile. you could use the following app, I believe it will fit your needs https://marketplace.atlassian.com/apps/1219125/mobile-for-jira-service-desk-portal?hosting=cloud&tab=overview https://play.google.com/store/apps/details?id=com.infosysta.mobile.mfjsdp We can help you with the…

yes, is that all the information you have on that tab? if I read this right the Waiting Cost Center Approval is the second status of the workflow and by the time it reaches there, the user is already added as approver, is that right? Assuming that all you see on the history tab is what I can see, and the user is already in…

Go to one of the issues that you need to fix and select the history tab and send a screenshot of it. I'd like to see the history records to see if that can help to identify what is happening

@Maikes could you share some print screens of the history tab? May be some leads to know where is this coming from or at least who is doing it.

Hello @Maikes the approver is a custom field that you would define which one you will use on a workflow status. So I would do the following. Within the project go to the workflow settings and edit the workflow associated to the issue type of your issue you want to edit. Check every status until you find the one that has…

Hi @Miguel Weber maybe what you need is an app like the following https://marketplace.atlassian.com/apps/1214127/abacus-jira-calculator?hosting=cloud&tab=overview That should allow you to do math based on the value of your other fields. Exporting to an Excel is simple as suggested by @Lenin Raj 

Yes, that shouldn't be an issue but in case it is try doing several imports with less issues per import

Hello @Yaniv Gal you need to create a screen and add it to the close transition. That way as you close the issue it will pop up a screen that will show such field

admin import url should be something like this https://yourcompany.atlassian.net/secure/admin/ExternalImport1.jspa

Hi @David Moore transitions work the same way regardless if you are using UI or via REST API. I suggest you play with your transition from the user interface until you are certain it does as it should (mainly because it's easier) and then when you do it via API you will see the same results

I don't know that one but most likely does, specially considering that shows available to install in your environment. It won't hurt to give them a try and see for yourself

@Meghana_H sorry for the delay. Is the custom field available on the screens? There is no need to make it required on the field configuration. Also, are you running the import as a standard user or as an administrator?

From the times I worked with the add-on I would say the answer is no. I can't think a way to have something like that in place

The service desk project should be configured to accept request from any customer not only those added to the project. That's what I suppose it's missing with the little information I have. Please add more detail if it wasn't the case