John Funk Community Champion

Hi Priyesh, JSM is charged by the JSM Agent and is separate and above the cost of the licenses for Jira Software Users. You can find pricing here: https://www.atlassian.com/software/jira/service-management/pricing

Absolutely it allows both Validators and Conditions in the same transition in the workflow. I have several.

Hi David - Welcome to the Atlassian Community! You can't string together workflows in that manner. But you can create a larger workflow with all of the statuses in it. Then control who does what by adding transitions between the statuses with Conditions. That's what we do. 

Sorry, I missed the part of your question about it being done with the API. There are other templates out there for Core - I suggest you look at those to see if there is one that is closer. Otherwise, you will have to do the manual updates after every project creation. 

Why don't you fix one of the Projects, and then create the other projects based on the one you "cleaned up"?

Hi Dionei, That is controlled with Conditions and/or Validators in the workflow itself, not Automation for Jira. Automation only performs a function based on an action taking place, and cannot prevent an action from taking place. If you can't modify the workflow because it is shared with other projects, then you will need…

Hi Michael, THe buttons at the top for the change in status are actually Transitions in your Workflow. So if you Edit your workflow, you will see them there. 

To create the board: 1. Create a new filter that looks like: project = CORE order by rank ASC where CORE is the business project you want to use. Be sure to save it and share it with whomever needs to see it. 2. Create a new board. 3. Base the new board on a Saved filter. Use the filter you created in Step 1. 4. For the…

Hi Ellis, I agree with @Guilhem Dupuy - there's probably no bad practice either way. If you are limited on the number of rules you can execute with Automation for Jira, then you might consider using post functions and triggers on the workflow. Otherwise, Automation allows you to not have to add the functionality to every…

Hi Atul - Welcome to the Atlassian Community! So, is the problem that you do not want the sales requests to come in as the Service Request issue type? If so, you need to create another Request Type and attach it to a different Issue Type. 

Hi Paul - I am not sure I am completely following your need, but let me make some observations. 1. No, you can't change the filter that comes with a Jira Core (i.e. Business type) Project. But have you actually tried to create a new board that uses a filter that includes the Business type projects? 2. With a Classic…

No, apparently that's not available for Cloud. So we are going the Atlassian Access path. 

Thanks to everyone involved with this today. Lots of good information and thanks for taking the time to answer questions!

Olá Fabrício - Bem-vindo à Comunidade Atlassian! Você pode ser um pouco mais descritivo em sua necessidade? O que exatamente você quer fazer?

Great! Glad it is working. Let me get someone to mark it as "solved". 

Well, this gets into the fact that there is no field level security in Jira Cloud. So the only route to go is based on what Kagithala alludes to below. But here is some more detail. 1. Create a new Transition Screen that has the fields you want people to update. 2. Create a looping Transition on each status in your…

Hi Brett - let me see if I understand the need. You would need to implement a condition on the transition from one status to another - say from status A to status B. In other words, do not allow the the card to move to status B if it is missing those things. You can implement that now with no problems. But your question…

Hi Michal - Modify the Permission Scheme for the project to grant the users the Schedule Issues permission. If you do not want them to create or edit issues, make sure they do not have those permissions in the same scheme. 

I can't tell you why the error messages are not adequate - that would probably be a good suggestion for you to provide to Atlassian. I will bring it up with my next personal interaction with someone in Product Management. Also, I almost always create a new project based on an existing project so that all of my current…

Hi Anupam - Welcome to the Atlassian Community! The only think I know to do in this scenario is to create another custom field and set it equal to the value of the Due Date when it is created or first populated. Then when it is changed, you can compare the new Due Date to the value in the custom field using JMWE or…

Hi Lily - The Archive a project function is only available for Jira Premium subscriptions. If you want to keep it but not be able to use it (archive it more or less), then create a permission scheme that has no permission for Create Issue in the scheme and attach it to the project. 

Can you get to the project settings for the TCLOUD project? If so, check the Permission Scheme to see if you are in a group or have access to the Browse Project permission. 

Hi @djones - Welcome to the Atlassian Community! So if you do a simple filter that says: project = TCLOUD you don't see any issues?

project = BIZ or (project = DIP and issuetype = Epic) ORDER by Rank ASC

Try this link: https://YourDomain.atlassian.net/jira/boards except replace YourDomain with your domain. :-)

Yes, that one. :-) So that filter should already show the Epics that are on the BIZ project. Now you will need to add the statuses for the Epics to the columns on the board. So while in Board Settings, go to Columns. Then either add new columns for the Epic statuses and drag those statuses from the far right hand side to…

Can you share the actual board filter? 

Can you share your filter and what you would like to see that it is not showing?

Hi Vanessa - Welcome to the Atlassian Community! In Jira Cloud, you cannot make a field mandatory based on the value of another field or linkage. You could make it mandatory as you transition an issue from one status to another using a third party add-on such as JMWE or ScriptRunner.