Rebekka Heilmann (viadee) Community Champion

Hi @Christian Wolfram are you referring to changes by the Agent in the issue? Or is the customer editing fields in the Request view (in the portal) - if so, are these fields part of a form or are you using a third party App to make Edits of "normal" fields possible?

Hi @Takuma Hanaya and welcome to the Community. There are two different user management experiences. Can you confirm which one you have? Check this for details: Remove product access for users | Atlassian Support It almost sounds like you are still on the old one. The article provides instructions for that two. It also…

Obviously me too - the order you chose (oldest to newest) is the correct one. So largest to smallest number top to bottom like in the screenshot gives you the correct results ;) well done! -> I edited my original reply so folks aren't confused.

Hi @Peter McGrath and welcome to the community! First of all: When you add an Issue link, the dropdown will give you inward and outward links. Usually, if the inward equals the outward description (like in "relates to") it should only show it once. So there might be a minor difference between the two or it is actual two…

Hi @Glabet Montenegro and welcome to the community! Can you share the Boards' filters with us? If you have one project with multiple boards you would have to differentiate between the components in the filter for each board.

Hi @Ronald Letona per default functionality, you can only sort fields into "Description", "Context", and "hide when empty". "Description" fields will show up on the main section - below/above the issue description depending on your config. Context fields will be under "Details". "Hide when empty" under "More fields" There…

Hi @Dilip T K and welcome to the community! The JQL will look something like this: "Start Date" <= -100d This will show all issues older than 100 days. If you sort your swimlanes newest to oldest issues top to bottom you don't even have to worry about restricting the Date to something like "between 100 and 500 days old".…

They are not automatically added to each project, but once created from either project, you can add the one and the same org to the other project.

Hi @Chris Tolley what are the reasons for the split, if essentialy everthing is shared? I would strongly advice against team-managed projects in this case, unless you want different configurations in the near future. With Company-Managed projects you can at least share Workflows, Issue Types and such without configuring it…

Ah, sorry. You are in a team managed project. Resolution is not supported in Team managed projects. Check out this: Set Resolution Field for Team Managed Project Jira Issues | Jira | Atlassian Documentation

Hi @Drew Montagna you need to add a Rule "Update an issue field". Remember to also clear the Resolution field when transitioning back out of a Done status. It works with the same rule.

@Martina Against all other advice (which still is, to link the Subtasks directly per "Blocks" Link Type - description provided by others) I managed to create a rule to achieve what you asked. Assuming that what you said in the last comment is true 100% of the time: 1. Trigger and conditions need to be adjusted to your…

The "automatically share" option should be activated, if you want all Requests from the Customer shared with their whole Organization. Which should be true in your case. Requests (Customer view on an issue) will be visible in the customer portal. Access through Channels > Portal > Open That's the Portal view, where you can…

Hi @serge calderara You can make the portal available for public access with not login required. Not sure what kind of portal that is and if that would be an issue. Some functionality in the backend will only work with registered users but for most Demo cases it's sufficient.

Hi @Beyer B. (Brian) The requests will be available in the Portal view, if they are shared with the Organization. You can change the default setting for that in the JSM Administration This has little to do with what your users will be used to, as they only will be able to comment and access whatever transitions are…

That's so random! Here in Germany we still mainly have Christian (mainly catholic) holidays (some areas more than others) and some historical ones. Coming from Cologne, we break up the long time between New Year and Easter by celebrating Karneval. It's not a public holiday but lots of schools will be closed from Thursday…

I am not telling you anything apart from: Be nice. This is a community that is dedicated to helping each other. Everyone on here spends their own (free) time to provide answers. Unless the tag next to the name says "Atlassian Team" we are all users like you. So if you want to provide product feedback I suggest opening a…

@ozama motohiro Not sure. I'd have to test it so you may as well ;) 

Hi @Martina I would 100% second @Trudy P Claspill in the suggestions to simplify the relation between the Subtasks. Even after reading the thread I am still not 100% sure of how you're issues are connected and what you are trying to achieve from a business point of view. Back to your current setup and automation rule, it…

Hi @Emil this is just a Workflow template. If you cannot "install" it, you can simply download and import. There is no major functionality behind it so i wouldn't worry about compatibility too much and simply try it out. You find the Import option in the settings, top right corner

Hi @Drew Montagna from what view are you trying to add the Status? My guess is, that you are trying to add a new status but a status with that name already exists on your Site. If you are using a company managed project then Status names need to be distinct. You can however add the existing status to your Workflow in the…

Thanks @Jack Brickey I wasn't really expecting a different answer but sometimes the Community is surprisingly creative ;) 

Are your customers sorted into Organisations? See this documentation: Group customers into organizations | Jira Service Management Cloud | Atlassian Support If you want all requests shared, simply put all customers into one Org. You then can edit the default share setting in the Jira Administration > Products > JSM:

Issue Level Security only works once the issue is created and doesn't stop anyone from creating an issue regardless the type.

Hi @Robert Anderson are you Site/Org Admin on both Sites? There is a fairly new "Copy data" feature available in the Org Administration: What product data is copied | Atlassian Support I've not tested it yet, though.

Hi @박성민(학해) does the error occur only when you try to search the Reporter field or any user field? Do you have the Browse Users permission? Is the Advanced Search (JQL) working as expected? Can you add the Reporter field to the "normal" Jira search (not in the Queue view but the general issue search)?

Hi @Devtech83 can you elaborate on what you understand as "Form"? Are you referring to the Request view or the issue view? What value can you choose in that field? I've not got anything called "groups" in our test instance in neither custom nor system fields.

Hi @TRẦN HIÊN and welcome to the Community, this will be a Marketplace App. Not sure which one. I only found Apps that will allow you to create Checklists outside of the Description field. If you need the function regularly check out: Jira apps | Atlassian Marketplace If it's a one time thing you can create Checklists if…

Hi @Inger Persson with Standard Jira this isn't possible. Permissions can only be based on projects but not on Issue Types within. You can achieve that with ScriptRunner behaviours though: Restricting Issue Types with ScriptRunner for Jira (adaptavist.com)

You still can do all of those things in Company managed projects. There were no changes in functionality for these classic projects in that respect. Team managed (next Gen) are simply following a different philosophy. They are made for a single team that wants to manage their own config and therefore will not be able to…