Dave Bosman _Inetum_ Expert

You can add those users to your environment and provide the license that way. 

So i forgot to answer a part. About the properties: If you edit your workflow and select a status, on the right side you have a link "Properties". If properties are added this could be the reason Examples of those properties can be found here

Hi @Dominik Henka So this is a step by step troubleshooting First, you need to check if the user that performs the action can edit the main issue. And with user i mean depending on how you wrote the plugin it can be the user that triggered the issue, but it also could be that it is a user specific to the plugin. For…

Hi @Dominik Henka So i repeat, what is the post function supposed to do? Regards Dave

Hi @Adakula Vinod See this question with the answer you are looking for. https://community.atlassian.com/t5/Jira-discussions/Shell-script-with-crontabs/td-p/1153459 Regards Dave

Hi @Fabien Frances You need to add a "branch rule / Related issues" in your automation instead of the "if" In type of "related issues" you need to select "JQL" and add your JQL in that screen. I think that will do the trick. ;) Regards Dave

Hi @Cristian Coianiz Unfortunatelly this is not possible. Maybe you should investigate on changing the notification scheme to the notifications that are really needed only. This could already have a huge impact. Regards Dave

Hi @Dominik Henka Is it really the same? You could have properties in 1 of the environments that forbid something. Also check your permission scheme. What is the post function that you want to perform? And if it belongs to a plugin, what plugin is it? Regards Dave

Hi @Colin Bosman Through the portal this is not possible You can only give them read access by providing them with a license and setting up your permission scheme correctly. Regards Dave

Hi @John Matrix To use insights you need a JSM license. If you set up your projects permissions correctly they wont have access to the projects. Regards Dave

Hi @Dominik Henka Most likely you are missing some configuration. However without more details it is hard to say what the root cause is. Regards Dave

Hi @Kapil Podduturi If you add project roles in your permission scheme, and you add a user in project A in that role, the user will not be able to see anything in project B unless you also add him/her in the project role in that project. So it is really project specific. If you want specific users to see all projects…

Hi @Sivaruban Kanagalingam First you will need to create a rule that will be triggered by the transition and does a check if the label is "Dev". Add a new branch related to the parent. Depending on if you use server or cloud you want to start a different action * In server you can trigger a new event. * In Cloud you could…

Hi @Jeff Boon You will need to create a security scheme and add at least 2 security levels. First security level would allow everyone to see the issue Second security level would allow allow everything else than role A and B to see it. See this documentation about security levels Then you will need to create an automation…

Hi @Neethu G Prem You need to add the field priority in your screens. So open all the screens you have there and then you can add the field. Afterwards it should work Regards Dave

Hi @sugirtha chandrasekaran Jira server is being discontinued. Only existing licenses are renewed until 2/2022 but new licenses and trials are not possible anymore. If you really want something installed locally you can create a trial license for datacenter on https://my.atlassian.com/license/evaluation Regards Dave

@RISHAV KUMAR GUPTA This is true in Cloud but not in Server. 

Hi @Observateur Jira will hide all fields in the view screen that are not filled in with the exception of some fields like labels, resolution, etc... And there is currently no setting that can overide this behaviour. There is a request for that, you can find it here So feel free to vote on it. Regards Dave

Hi @Ezadin Mahmoud Unfortunately it is because of limitations in Cloud that it is not possible. see here This also means that other develepors would run into the same problems. So the real question here would be, what functionality are you expecting because maybe there is a workaround for what you need. Regards Dave

Hi @Evgeniy Terekhov In my opnion it all depends on the expectations. If you are willing to do without some of the customizations I would recommend moving to Cloud. If the customizations are really needed you have no other option than using DC. Both have their pro's and con's. * The migration to Cloud will take up a lot…

Hi @Karol Horosin In that example that you sent, it is only the one user that is impacted for as far as i understand. It is because that email address is blocked due to the error sent back to atlassian. However this should be solved by resending the mail…

@Karol Horosin This has nothing to do with Atlassian but with the provider for your email address so you will be need to contact them. Regards Dave

Hi @communication12_ I think that Jira Software premium would be the best option. But without knowing all the details this is hard to say. see https://www.atlassian.com/software/jira/pricing for a comparison. As a team member of an Atlassian partner I would suggest that you buy your license through an Atlassian partner as…

Hi @Xingyuan Song SXY 宋兴远 You could create the user again with the same username. But i presume that you do not need that user to manage the issues anymore, so you could just create a filter like assignee = username and perform a bulk change and edit the assignee to someone that still exists in Jira. Regards Dave

Hi Omar, I could tell you but that would be me, saying in my own words, what is explained on this page ;) https://confluence.atlassian.com/cloudkb/best-practices-on-using-the-resolution-field-968660796.html The documentation is more extensive than what i would write here, so.... I hope this will help you any further. What…

Hi Omar, Very good question, When is done, done... You can find more info on the definition of done on scrum.org The burndown chart will check if the resolution has been set. Only when the resolution is set, jira will consider it as done. no mather what the status name is. Regards Dave

Hi Jitesh, To be honest, it is not a good idea to have so many values as it will impact performance. Is there any specific reason that you need this many values? Can it be done in another way? That being said, you should check the REST API.…

Hi Tim, Out of the box it is not possible in cloud. There is a feature request for this. https://jira.atlassian.com/browse/JSDCLOUD-1515 But you can solve it with this plugin. https://marketplace.atlassian.com/apps/1211016/canned-responses-pro-templates-for-jira?tab=overview&hosting=cloud see…

HI @[deleted] JSM has some automation out of the box but Software does not. If you need automation for software you need the plugin Automation for Jira. Do you have that and is it active? Regards Dave