Comments
-
Hola @Alvaro chico gonzalez bienvenido a la comunidad. Para ser usuario de la organización deben ser parte del grupo site-admin. Aquellos que pertenezcan al mismo pueden sacar y agregar usuarios al mismo. Pasa lo mismo con el grupo jira-administrators que son administradores con menos privilegios. Te recomiendo que dejen…
-
What I'm saying is the same thing that @Nic Brough -Adaptavist- suggested as well. Project import isn't the same as CSV import, that one will be the one with bigger chances of losing data as part of the migration. I wouldn't recommend that. I believe that project configurator can help you with the project import option…
-
Hello @Francesca Myerson if you need a big picture across many tools and instances you would need to consider Jira Align for that. I don't see it very likely/reliable that you will be able to do this without it.
-
Hello @milan_shah duplicating the environment and then removing from each of them the information and users that don't apply to them is the fastest way. If the backup size is too big, I wouldn't suggest you try to edit it, I've done that in the past to update URLs before restoring in order to point to the new instance but…
-
Hello @[deleted] welcome to the community. Looks like you have a kanban board with backlog, not a scrum board. If you want the second one, you will have to create a new one. If you want the classic kanban board you have to configure the one you see and remove the status you have associated to the backlog from there and…
-
Thanks but I don't think I'll need it at this point. Glad to know that you got what you wanted
-
Hello @[deleted] welcome to the community, don't hesitate to ask here if you need anything
-
Whoever is a Jira user. You must have an account to see the content
-
Hello @Veselin Takev that would be a very long list. You can go to the marketplace and check all the apps that are there and filter by tool and environment https://marketplace.atlassian.com/
-
Check out the following link then https://confluence.atlassian.com/adminjiracloud/creating-issues-and-comments-from-email-779288896.html You could configure the emails there so emails sent to account A end in A project for example
-
Yes, free plan allows everyone to see everything
-
Hello @Kevin Kendell welcome to the community, what you are looking for isn't available in Jira but maybe you could have an epic for this icebox and put tickets there. That way, if you show the epics on the board, there will be a place where to easily find them and drop the issues as well
-
Hello @E2131-Osman welcome to the community. A good way to improve nowadays can be by taking Atlassian free trainings that are around now. Check them in the following link. https://training.atlassian.com/free-training-catalog Regards
-
Give it a shot if you haven't already. I know it works with internal custom fields just haven't used it for that scenario in the past so I'm not sure if it's going to be a real solution or not
-
Hello @Amit Kanudia welcome to the community, based on what you say, if the email accounts are from your domain you create them on your email provider. Then you can add them in Jira as incoming mail handlers. I'm not sure that's really the question here though, could you please clarify further what you expect with this as…
-
Hello @Ivan Bagaev if it's the free plan, then it will be whoever has access to Jira. When you are using standard or premium plan you can configure Jira to limit the access to certain projects to specific users. Even within the project itself you could restrict visibility of certain issues as well.
-
As far as I know you can't change that setting.
-
Hello @Dirk Ronsmans maybe you can achieve this using elements app. https://marketplace.atlassian.com/apps/23337/elements-connect-formerly-nfeed?hosting=cloud&tab=overview If the group and users would be in an external database I'm certain it would be feasible. Maybe you can solve it directly using the Jira groups.
-
No, that is still not supported but apparently there is work in progress, see here https://jira.atlassian.com/browse/CLOUD-6999
-
Hello @Gulnaz Valieva I would suggest you start by doing clean up. As @Mathis Hellensberg you have plenty of issue types and most likely custom fields as well, I can't tell how many users you have but I've setup environments with less than 300 custom fields in which there were more than 3500 projects and 200.000 users.…
-
Hola @u607047 bienvenido a la comunidad, debes de ser system admin para poder gestionar los usuarios de la instancia. Si no ves la opción usuarios dentro de las opciones de administrador te están faltando permisos para administrar esto.
-
Hello @Martin Eagle if you go directly to the Atlassian url happens the same? As far as I know you can't have a custom domain when you are using cloud. I'm not sure which changes you made on the DNS records take it this far but I suppose the failure is related to it.
-
Hello @Lujain Falaileh there is no downgrade option in Jira so a roll back would imply restoring an older backup, therefore whatever happened after the upgrade will be lost
-
Hello @Sachin P welcome to the community, a board as you well mentioned is based on a filter. The issues that a board shows depend on that and if a ticket applies to both boards the information shown will be the same because it's only one issue. So in this case it's the ticket that is assigned to the Sprint doesn't matter…
-
Hello @Alex R. welcome to the community, as far as I am aware that feature isn't in place yet.
-
glad to know it's solved, I would suggest you mark this as such
-
No worries, your concern was solved, that's the goal here anyway
-
@Brent Mahaffey by removing them from the customers list should do the trick. Make sure that the customer permissions settings for the projects is set to only customers added to the project as well or they might end up again on the project if everyone can file tickets there
-
Hello @Craig Barrett you should check the permission scheme and see who can delete issues. This could change from project to project. I recommend that you assign a role to have such permissions and you add whoever is needed there. try to avoid adding users to the permission scheme
-
Hello @m.kitavujja welcome to the community, fields security app would allow you to do this. https://marketplace.atlassian.com/apps/23216/field-security-plugin-for-jira?hosting=server&tab=overview