Dick Community Champion

Hi @Lisa Echeverria , Welcome to the Atlassian Community. There's three kinds of admin (levels); * Organizational Admin * Jira Admin * Project Admin Depending on your own role in the Jira chain of command, One or more of these admins could have modified your access privileges. Hope your find out which, Dick

Hi @Roman Hryshchenko Welcome to the Atlassian Community First, you log into admin.atlassian.com and select your company. Then under the tab Directory, you find the Users. The filter in black allows you to select the Status of the users you would like to see ( Active, Suspended or Deactivated) and the Role you would like…

Hi @Tom Zhang , Welcome to the Atlassian Community From your posted picture, I can see the project has some restrictions in place. If your access level is too low, you might be excluded from editing a ticket. Hope this helps, Dick

Hi @JasonSylvester , If you've set it up, you're the Jira admin... The above procedure is only necessary when there are more than one project making use of the same workflow that you're using in your project. If that's not the case, just edit the workflow to your hearts content. Dick

Hi @JasonSylvester Welcome to the Atlassian Community. At first glance, it appears that someone removed the status "Review" altogether from your project workflow. Normally, deletion of a status can't be done without first moving affected issues to another project or status or Jira will pipe up with this message: Also,…

I'm glad you got your bearings, @Ilanguak Olsen. Don't forget, this community is a treasure-trove when it comes to helpful answers. Thank you for marking the answer, it makes this solution easier to find for people with a similar question. Dick

Hi @Robert Nadon DC sorely misses the foreach function in automation. It can only be mimicked somewhat by "doing the required stuff" when an issue is updated (and a proper initiation to all relevant tickets beforehand). Dick

Hi @Ilanguak Olsen, welcome to the Atlassian Community. You can attach a (custom) screen to a status transition (click the arrow in the diagram representation of the workflow you use in the project). This screen can hold your custom field to be set by the user doing the transition. You can make the custom field mandatory…

Hi @[deleted] Going from the data you've shared: There's still two filters active that could influence the outcome of the total issues found: * Exclude any completed issues after: 100 days. * The issue could've been in a previous release. Both can be checked by looking/editing the missing issue. Hope you get all your…

Hi @Bharat Patel Actually there's a workaround for your problem: use of Teams in the Plan / Roadmap. Plan - View Settings lets you group by Teams. Teams are defined inside the Plan as well. Once you use the project lead name as (part of) the team name, issues coupled to that team will show up using the name of the Project…

Hi @Bharat Patel Welcome to the Atlassian Community. You can incorporate custom fields in your plan using the settings cog-wheel (settings). You can find the tab Custom fields there. Hope this helps, Dick

Hi @Lubna Malik Yes this is possible! You would need two custom field to store the number of times a ticket is sent back (one for tickets from PreProd, one counter for tickets from Testing). An automation on the status change of a ticket can be set to fire if the smart value {{issue.status.fromString}} would be Prod…

Organizational admins do not use Jira for their work, they log into Atlassian's dedicated page: Atlassian Administration and then choose the organization they need to work on.

Hi @Shaikh Abdul Rehman It is highly likely that your organization admin (for all Atlassian Cloud access) is responsible for the undesired product access that you're observing. He/she can form groups to be able to manage the specific security you need. Hope this solves your unexpected guest problem Dick

Hi @Anuja Ariyaratne Welcome to the Atlassian Community You can find a card layout tab in the board configuration menu. The two pulldown menus on that page hold all custom fields available to your project. Hope this helps you get the data on your cards, Dick

Hello Hannah, You can find the 2 weeks setting under board configuration, general, bottom line. You need to be board admin to be able to change that. Hope this helps, Dick

Hi @Vidya VASUDEVAN , Please be aware that a board is not a project. A board is just like a pair of glasses that you use to look at part(s) of project(s). Like me, you can have more than one pairs of glasses (boards in a project). The custom field is declared for a project or multiple projects (these projects form the…

Hi @Sabine Benz-Reichel , welcome to the Atlassian Community You can set issue security for the projects you like to be excluded. You find this setting under Project settings. Hope this helps, Dick

Hi @Melissa C, Does the line of thought given above resonate with you? I welcome your feedback in this regard. Dick

Hi @Jürgen Wieser , An automation always needs to know on which issues it needs to work. This is not the case in your situation. The rule builder tells you to adjust your automation with the for each branch. This branch can be adorned by JQL like: Project = "XYZ" and status != Done to yield the issues you would like to be…

Thank you @Rilwan Ahmed , I was looking in the wrong spot (system fields list, home of all the system fields. The interface is a bit inconsistent here. I would've liked that list to hold editing possibilities as well, similar to those in the custom fields list. Actually, the description system field has some additional…

Hi @omranmiraouui , welcome to the Atlassian Community. Just using Jira, you can perform a search for tickets that are not in status "Done" and older than 30 days using the updated field. updated <= -30d and status != done order by updated By looking at the key of the issues, you see the projects that are inactive or need…

With respect @Rilwan Ahmed, but I don't think that @Arun Prasath question is about using it in a ticket. The way I read it, Arun would like to have another item in the resolutions list. Sadly, this is a system field that doesn't allow modification of the list items. Thanks for asking, it might be worthwhile to check future…

Hi @Barbora Kutikova ad 1: Make sure that the Actor of automation rules is set to a non-personal account: JiraBot! All issues that JiraBot creates, have JiraBot as the reporter, JiraBot will receive the email notifications! Using a bot this way is also good practice, people will know the issue is made by an automation. It…

Hi @Digvijay Singh Gehlot I looked at your logic in the automation and was wondering if you can replace it using a single lookupissue using jql and then from the number of elements returned, adjust the status of the initiative. lookupissues = project in (CRIS, GIB) and "parent link" = {{issue.key}} and status =…

Hi @Travis Hill I'm not a marketplace entrepreneur, but we're currently evaluating the plugin JXL. It does the exact thing for you: you can have a summary line on each hierarchical level that you want. It works flawlessly with the system status field, so you would need to amend your workflow to mimic the statuses mentioned…

Hi @Pierre Guyénot It is not there, but you can have an automation triggered by the status change of the epic and check it's children. If not all children are in the done status, you "repair" the epic status with the {{triggerissue.status.fromString}} value. Not ideal, but practical, Dick

@Si Walker It's true, this quarter Atlassian has scheduled work on homogenizing the child parent relationship across all issue types using the parent link field. It's way more cleaner than maintaining the odd-one-out epic link field that I still have to use (we're running an older Long Term Support version of Jira…

Hi Si it's all in the Create Issue step where you link the task to the epic. Using the dropdown with the <Cog icon> Choose fields to set, you can select multiple fields to fill. Check the Epic Link entry in the dropdown, and you can fill it with the Current issue reference as depicted below:

Hi @Si Walker , welcome to the Atlassian Community! Yes, automations can generate fully filled tasks and sub-tasks for you, when an epic is created. You wouldn't need a marketplace app. You can "nest' tasks under an epic by setting the epic link field to the newly created epic key. Hope this helps, Dick