Alex Koxaras -Relational- Community Champion

Hi @Martin Sköld and welcome to the community, No the transition option are not disabled on the free plan. However in your image you have selected a status (to activate the global transition). But to see all the available options, you have to select the "all" transition (arrow that points to Done status). Hope that helps!…

Hi @Nicolas Embriz and welcome to the community! Issue collectors may be used for such things you describe. However this collector do not work inside Jira cloud, but via another website. You can learn more about them here https://support.atlassian.com/jira-cloud-administration/docs/use-the-issue-collector/ Another way to…

Hi @Vikram Raj and welcome to the community! Can you please elaborate a bit more about the reporting template? Where exactly do you refer to? What kind of projects are these 30 projects? Software, JSM?

Hi @Martin Mussel and welcome to the community! You can user Jira's shortcuts to do many things: Moving to the next/previous issue on a project while viewing only the issue list, is a piece of cake (use j or k). However I don't think that it's feasible to move to a previously working issue, unless this issue was on a list…

Hi @amit_bakst It's not wrong what you did. This will work perfectly fine. However Atlassian propose in project permissions to user project roles rather than group, only because a project administrator can grant membership to users and group he/she belongs to. If the project admin wants to grant a user special permissions…

Hi @Peter Jongsma You can achieve that by using events and the notification scheme. E.g. let's say that you need to add these reviewers during a transition. On that transition you would have a screen for the user to add all reviewers. * You have to create a new event called e.g. "Notify Reviewers". * On the previous…

Unfortunately you can't do that. At least not in the way you think of it. My last statement about watchers stands. What you can do is to: * Create a new project role called "Viewer" or "Watchers" (I wouldn't use the latter, just to avoid confusion) * Create a new permission scheme * Grant the browse project permissions to…

Hi @Kelly Hawke Watchers are not a project role, or a group, or a custom field. You can't grant them this permission. However, if a user has the browse project permission (we don't take into account the security level) he/she can become a watcher. What exactly are you trying to achieve? Can you please elaborate? Cheers,…

Hi @Tiffany Li , What is your goal here? To check if the request participants field contain some of the users inside an organization? And then what? Add those who belong in the organization and are not part of the request participants field?

Satish the "Browse Project Permission" is the most important permissions of all. If you don't have this permission, you are not able to see the project -> not able to see issues -> not able to edit issues -> etc etc I hope you get my point. So giving membership to users with that specific permission is important if you…

Hi @Satish Uppari and welcome to the community! From what I can understand from your question, is that you don't have visibility over certain issues. Try adding yourself to this project and try again. If that will not solve the issue, then please provide screenshots of: * your project settings people memberships * other…

Hi @Olivier Nipshagen and welcome to the community! How did you add this user to a project? You gave membership to him directly or via a group. From what is seems you: * Added this user to a group with product access * This group was added to all projects with a project role * This project role was associated of course…

Hi @Sarah.Fuller and welcome to the community! Does this problem persists to your colleagues as well, I would suggest you to raise a request on Atlassian support (https://support.atlassian.com/contact/) if you are indeed on a paid plan. Atlassian team will look into this issue and provide any feedback. Hope it helps! Alex

Hi @Lea Le Borgne and welcome to the community! If this problem persists not only to you, but also to your colleagues, I would suggest you to raise a request on Atlassian support (https://support.atlassian.com/contact/) if you are indeed on a paid plan. Atlassian team will look into this issue and provide any feedback.…

Hi @Keerthan Rai I think that resolved by is a custom field and not a systemic field. This means that a jira admin has created this field and placed it on certain workflows/automations etc. If you have access to the workflows and edit them (if you are a jira admin) then we can help you. Also it would be good if you clarify…

Glad to know that this helped you.

@Alex here's the deal: When creating the issue, most likely the system (even if you move the PF after the reindex) didnt update the Processing field value. This result in a null value, even from the very beginning. That's why you are getting the null on your table. Now, I would consider two alternative to this: * Instead…

@Alex thank you! I managed to reproduce your error and I get a null as well. Let me try something and get back to you.

@Alex when does this clone listener is triggered? In which events? And how exactly you want it to work? I mean you have a parent issue (e.g. PAR-1). When you edit this issue, then this issue gets cloned and created PAR-2 as a task with the table as the description Is the above statement correct? If not, kindly clarify.

@Alex I tried the same thing on a DC instance, with the latest script runner, and within the Clone prebuilt listener, and it seems to work well.

Glad to be of assistance!

Good to know that this helped you!

Hi @Alex What is the result you are getting? What do you mean it doesn't work? Is there any error on your code, or simply the table isn't populated in the description? Or the table isn't in the correct format? And where do you place this code? On a listener?

Brian, I believe that you are in the right direction, considering all the inputs you provided here. The reason I asked you, is simply because there was no apparent reason for you to move, and save all the trouble. However, as I said, you are correct in considering moving to a JSM project. You can use the free plan to cover…

Hi @schapsl I would be in favor of "one project to rule them all", if and only if all project share common ground. E.g. if you are developing websites, then I see no reason of having each website to its own project. If you develop e.g. mobile apps, and you develop them cross platform, and again share most of the settings…

Hi @Brian Hennessey I would create a new JSM project and try to share settings with the existing project you have. This will result in having certain shared schemes, such as notification, screen, permission, issue type, workflow etc. This will be very handy, since you don't want to lose any data (data are stored in fields,…

Hi @Sarah Talebi and welcome to the community. Not sure that you posted your question in the right place, but I'll proceed by assuming that you did. Obviously, someone told you that you should contact your Jira Admin (but I'll add "your Project Admin" as well) so that he/she will remove your from the projects you want to…

Hi @Michael Marriott After the trigger add a branch rule only for the current issue: The add any component you want inside this branch. Hope that this is what you were looking for. Regards, Alex

Hi @Michael Green As @Sri Kumar very well guided you on these specific JQL functions, I'll provide your queries * resolutiondate >= startOfDay() * resolutiondate >= startOfDay(-1) and resolutiondate <= endOfDay(-1) Regards, Alex

Hi @RNV Jira1 and welcome to the community! Try the following, it worked for me: * Create a rule * Add as trigger "Field Value Change" and select all numeric fields you want to this rule to get triggered * Create a variable with a name "maxValue" and…