John Funk Community Champion

Hi Nishant - Welcome to the Atlassian Community! Team-managed projects do not have components out of the box yet. You can vote for the request and follow it here: https://jira.atlassian.com/browse/JSWCLOUD-17601 Also, take a look at this article by a third party vendor by @Nikki Zavadska _Appfire_…

Hi Sudhanshu - I am not aware of Atlassian's timeline for this, but here are some links that might help you. The first is the roadmap for Jira products, including Team-managed projects: https://www.atlassian.com/software/jira/whats-new/next-gen?_ga=2.104316484.513035551.1586779195-1313086432.1576012938#intheworks The next…

Hi Andrew - Welcome to the Atlassian Community! What type of project have you created? Most project types are very limited in how you can modify the board. 

Those steps I outlined right about your last comment. :-)

Hi Damir - Welcome to the Atlassian Community! I do not see a request for you that is still open. Could it have been under a different name? Also, this one is coming to a close - just waiting on users to take their exams. You are probably better off requesting access to a later class. 

Sure - go to Settings > Issues > Workflows Find the workflow that the project is using Click on Edit Click on the line going to the status that you are trying to transition to That will popup a box on the right side. Check to see if there is any value for the Validators and Conditions options. Then click into those to see…

Hi Michael, I see that sometimes when there is a Validator or a Condition on the transition. I would check that first to see if either of those exist and whether you are excluded from the checks. 

Hi Kazakov, 500 errors are slippery things. I used to get them a lot when I didn't have contexts attached to all of my custom fields. I would start there first. 

Hi Josh - Welcome to the Atlassian Community! Check the Permission Scheme associated with the project to see who has the Browse Project permission. It might be based on Project Roles. If so make sure the project role(s) that have that permission are linked to the group under People. 

Hello and Welcome, Vincent! We are glad you are here!!

Yes, it seems to have cleared itself up as it rolled into June. :-)

Hello and Welcome, Kodi! We are glad you are here!!

Hi Curt - I see the same error. @Jane Yeoh 

I am afraid that doesn't help any. Can you answer my last question? If there has been an issue that is approved, what do the values look like in the fields for that issue for the Approver field(s)?

こんにちは @wakiya 現在のワークフローのコピーを作成する必要があります。次に、上記のプロセスで最初に行ったように変更を加えます。 次に、新しい (非アクティブな) ワークフローを既存のワークフロー スキームに追加します。

Hi @박보은 Maybe try moving the last two items under the branch - putting them where the word Component is in your image. 

Sim, está correto. Tem a ver com a Epopéia e não com o Projeto.

You are welcome 😊

Hi Augusto, Piggybacking off what Trudy said, I usually set a custom field value for that. I literally have a custom field called Generic Yes Field. It is a checklist field with just one value - Yes. When the first automation fires to that Status, then set the value of the field to Yes. In your automation rule, check to…

Hi Matthew, In your example image above, that's because the Issue Type you are moving to/converting to, uses a different workflow. It might be in the past that two different issue types used the same workflow and then you can simple change the value of the Issue Type in the issue itself. But not so if they use different…

Hi Sangeetha, The ScriptRunner Behaviours tool that can accomplish this is only available on the Jira Server version. There is currently no way to do this in the Cloud. 

Automation For Jira won't create new fields themselves - it can just update values in existing fields. 

Hi Andrew, I suspect it is another tool you have running that is doing that, and not Jira itself. Maybe something in your browser or laptop/phone. I have never had "Jira" autocorrect my typing. 

Hi Richard - Welcome to the Atlassian Community! You need to modify the Field Configuration used by that project. Go to Settings > Issues > Field configurations Search for the one used by the project and edit the configuration Search for the field you want to be mandatory and click the Required option. 

DOH! Good catch, Jack! I did a View Source on the Project Details page and then did a search for: "project","id": That showed me the ID value

Sorry - I lost the notification of your update in my email. I do not use the built in automation that comes with JSM projects. I just use the Automation For Jira add-on because it gives more functionality and better notifications when something doesn't work. There is a Free Lite version and a paid Pro version if you are…

I would go ahead and submit a support ticket with Atlassian for that: https://support.atlassian.com/contact/#/

Hi @ihe - Your assumption looks correct to me. Is the second rule not firing at all? i.e. There is noting in the audit log when after rule 1 fires? Are you sure rule 2 is active? Have you done a simple test to change Field B direct - outside of Rule 1 firing? And does that work? 

Marco - It will look like: pid=14800 Does your URL not show that? Maybe try another browser? 

I am doing very well - thank you. Are there many Jira users in Kathmandu?