John Funk Community Champion

Actually it’s probably because you need Jira Software and not just Jira Core

Hi Anthony - Welcome to the Atlassian Community! No, each person viewing information in Jira will need a license. Jira Service Management has a concept of Customers who can be public and enter and see information. 

Go to Settings > User Management Then either click on Groups and see who is in that group, or click on your name and see what groups you are in. :-)

Hi Stacie - Welcome to the Atlassian Community! This is currently not possible as Releases are created per project. You could create a release in each project with the exact same name. But they won't be truly shared. 

Hi Rupert - Welcome to the Atlassian Community! Sometimes this is just a temporary thing. I would give it a little while and then try again. Maybe even disconnect and reconnect. Is it just one column? Or all of them? Can you edit columns on other boards? 

Hi Saritha, Make sure you have Jira Administrator privileges - that you are in the administrators group. Then go to Settings > System > Global Permissions and make sure you have Administer Jira permissions. 

Hi Arjen - Welcome to the Atlassian Community! Allowing that to be added is usually a part of the agreement you allow when you purchases/install the add-on. So I don't think you will be able to prevent it doing the initial adding to the permission scheme. Also, they usually do it for a reason, so removing those from the…

Try changing the branch to Most Recently Created Issue instead of the All Created Issues that you have. 

Hi Jason, I don't believe this is possible yet. Take a look at this request and vote for and follow it: https://jira.atlassian.com/browse/JSWCLOUD-18677

Hello and Welcome to the Atlassian Community, Manisha! We are glad you are here. 

Hi Devon - Welcome to the Atlassian Community! Check your board filter to make sure that you have an Order By Rank at the end of it. You must have that to be able to drag tickets vertically. If that's okay, then also check to make sure that you have Schedule issues permissions in the Permission Scheme for that project. As…

Hi Jamsahaid, Why don't you just use Automation For Jira to do all of that? You don't need to write scripts or code and it will do all that you need. Here is some more information to get you started: There are two types of automation: * Global: In the Free version, you get 100 executions per product, per month *…

Hi Jothi - Welcome to the Atlassian Community! I do not use Big Picture, but make sure your Edit screen for that project and issue type has the End Date on it. Otherwise, you will probably need to contact Big Picture support. 

Maybe it will work if you have a space on each side of the value. 

Hi Mick - Check your Board filter and sub-filter to see what it is actually letting through. When cards are created, they will flash the message you see and then end up in the first status in your Workflow. That's usually Backlog. But check your workflow for sure - yours might be the To Describe status. 

Hi Daniel, The short answer is no, JSM/JSD customers cannot see any project issues except for JSM/JSD projects. 

Hi @Christopher Tom - Welcome to the Atlassian Community! I don't know of anyway you can do this unless you add some type of custom field and then create swimlanes based on the values in the new field. 

Overall, I am definitely a donut and cinnamon roll person. If those are around, I can't keep from eating them. 

https://community.atlassian.com/t5/Off-topic-discussions/Friday-Fun-Cupcakes-for-all/m-p/1532293#M10109%3Futm_source=atlcomm&utm_medium=email&utm_campaign=immediate_general_reply&utm_content=topic

Same for me

1. Yes, you can add initiatives above the Epic. Here is guidance for that: https://confluence.atlassian.com/advancedroadmapscloud/configuring-hierarchy-levels-998650959.html 2. Regardless, you should be able to use the same Epic on multiple boards 3. Yes, it should, although I have not directly tried that. 

This an example of what it could look like: In the ProForma setup, it would look like this:

The basic rule is that you should start with what you have now as a process. Map out the workflow based on that. Then take a look at your process to see if anything looks wonky or has too many steps and adjust your process from there. There are so many rules and situations that have to be done at each school district or…

That's really weird. Since the Old Jira Issue View is going away, you might want to concentrate on making the change in the New Jira Issue View. 

Yes to the first question and No to the second question. So your email could look like: {{issue.field 1}} {{issue.field 2}} {{issue.field 3}} {{issue.field 4}} {{issue.field 5}} etc. But if there is no value in fields 5, 6, and 7 there would be a big gap between line 4 and line 8 - they would not move up. But I would see…

Hi Sandhya - Welcome to the Atlassian Community! For a Classic Software Project, you can go to Project Settings then click on Issue Types in the left hand menu. From there, click on Actions and select Add issue types Then add your new issue type and save. At that point the new issue type should be available for the…

Maybe put a space on each side of the / - FE10Z200507M03 / F4405200602H06/

Can you post the full rule? I only see the part starting with a Condition. 

Actually, that's what I do - I don't use any labels/headings for the fields, but just list the issue fields themselves. It the scenario of using conditions, you would have If then else logic for each field is empty condition and then the email for that condition. You would have to copy and paste the email x number of times…

What is in the Branch rule? That's what's failing. And actually, why do you even have a branch?