Alex Koxaras -Relational- Community Champion

Both of them will do the trick. But I was referring to adding a transition screen with the required fields.

That will do the trick. I can confirm this. However, it's not the best of ways :/ Add Time tracking field for original estimate, and log work field for logging the work.

Hmm... then most likely you have to add a transition screen with the required field. I believe that this validator needs the fields to not be empty during the transition. Try adding a transition screen with this (these fields). Otherwise with the use of an app, like JMWE this could be done more easily.

Are you populating both fields?

Hi @jonathank and welcome to the community! Try the following rule, because I've tested it and works: The problem with your rule was that even if the issue was unassigned, then the last component will be executed no mater what! Is outside of the if/else statement. So you will edit the description always.

Hi @Thembisa Ndlamlenze Try the following please by adding original estimate and time spent: * Edit your workflow * Add validator "Field Required" * Choose all the fields you want NOT to be empty during the transition * Click add * Click publish This is just to see the transition overview. Don't forget to publish the…

Hi @Christian Heimerl and welcome to the community! You can remove the notification scheme from the project, and that will immediately stop sending notifications for that specific project. * Project Settings > Notifications * Edit Notification Scheme > Select None

Kindly accept my answer in order to help other in the community! Thank you :)

Hi @Sam Gamblin and welcome to the community! You can't do that per se. Jira uses the rank field to sort issues, and there isn't a functionality to move the card to the top of the list. You can only move the card to a different status.

Nice! Kindly mark my answer as accepted, in order to help others in the community! Thanx!

Hi @Jason Liu Approvers and approvals in general exist only in JSM projects and not in Jira Software. Having said that: * You need to have two outbound transition from the Need approval status. One for approve, and one for decline * After setting up the above, you have to activate your workflow by associating it with an…

Hi @Martin McGovern , Short answer is no. You can't have this out of the box. JSM email handler is configured to get only email's subject which will be used as a summary, and body which will be used as description. Keep in mind that Jira only needs a summary to create an issue. Having said that, you could potentially…

Aha! So what you need is the user to have different create screen fields, for the (at least) two different issue types, right? E.g. for the task (I'll use the Epic issue type for demonstration purposes) and for the bug If that's the case, then you need two create at least two different screen schemes, one foe each issue…

@Bogomil Shopov if that's ok with you, kindly try to reply to the thread I've created, to keep the conversation consistent. Now, your rule is ok. Try refreshing the page, and take a look at the audit log. It should mark "Success".

Hi @Bogomil Shopov and welcome to the community! The thing is that Jira do not see the initial selection of issue type as a change. Therefore the rule will not trigger. What I would do is just to: * On issue create * If issue type = bug* Then do something Hope I make myself clear. Let me know if you need any clarifications.

Once you find out, kindly update this thread. Cheers!

@Tabatha Spake any screenshot will help However, take a look at his documentation -> https://support.atlassian.com/jira-service-management-cloud/docs/how-global-permissions-affect-project-permissions/

Can you see if now they are in the request participant field? If not, add them and try to update an issue. Since you have already checked that all customers involved will receive notifications, then they will.

Customers do not need a license. But their abilities to do stuff are quite limited. Besides that's the whole reason of having a service desk. Few agents with paid license, and infinite customers.

@Aaron Andrade did you find what was causing it?

Well, what version of Jira are you using?

Good to know and glad it's solved!

@Nikhil Jagshettiwar go to cog > system > global permissions There you have to see to which groups he/she belongs to. Then make a decision about: * Whether to add him/her to an existing group which have that global permission * or create a new one, put him/her on that group and then give this group the specific permission

@Gabriel Cassi , First of all there can be only one assignee (on that specific field). However, you can always add another agent as watcher, or you can even create a custom field (user single or multi) and add there the rest of the agents. However, you have to modify your notification scheme, in order for the users within…

Hi @Markus Kokemor and welcome to the community! If you can't create a new project, then you might not have the necessary global permission of Administer Jira, with which you can create projects. Ask your Jira Admin to grant you that permission, or to create a project for you. Read more about permissions here…

Hi @Andy Elson and welcome to the community! Perhaps some customers are duplicates across projects? Is there such a case?

But @Mariam Slade you can change your customers' name manually * Cog > User management > Jira Service Management

@Mariam Slade If you have setup your portal like this: Then of course you'll get a result like the following: If on the other hand, you don't allow sending requests without logging, then a customer upon signup can easily do the following:

Hi @Patryk B and welcome to the community! I have no idea who's asking you that, but I haven't seen that specific feature anywhere... :/ Having said that, this can't be done with the functionalities that Confluence offers. Permissions and page restrictions are set from specific parts and only from space/confluence admins.…

Hi @Mariam Slade and welcome to the community! Let's start by assuming that you are working on a project of Jira Service Management. All customers that are allowed to send email to a JSM project, must create an account (except if you have setup your JSM project to allow emails from anyone on the web). When they create an…