John Funk Community Champion

No, you cannot allow some users to hide a field and others not to hide it. It either shows for all or hidden for all. 

Are we talking about dashboards or Kanban boards? They are two different things. 

Hi Absa, Atlassian is not selling anymore licenses for Jira Server and is phasing out support next year. You should not be migrating backwards. 

They won't be able to respond to JSW links because they need a license to see those. They will only get updates from comments on the JSM project. You might could try an automation rule that copies a comment on the JSW project by the developer to the JSM project. And also have the JSW project move the issue in the original…

HI Suzy - Welcome to the Atlassian Community! I don't believe those types of custom fields are available to Automation For Jira for Team-managed projects yet. You might want to click on the Give Feedback link on the bottom left of the project menu and let them know you would like to have it. 

Hi @Foxcliffe Hickory - No, you are not going to be able to move that. 

Hi Enrico - Welcome to the Atlassian Community! Give this a try: status = "X" AND Component = "Y" AND ((labels != ENplatformAchecked AND labels != ENplatformBchecked and labels is not empty) OR labels is empty)order by created DESC

Okay, let's start back here first. What type of project are you using? Team-managed? Company-managed? Jira Work Management? 

Hi Dinesh - Welcome to the Atlassian Community! That is an extremely large question. Yes, it can do both - but you need to narrow down your question(s) to something more manageable to answer. 

Hi Akshith, If you use Automation for Jira to clone the issue, then, yes you can. 

Hi Sierra - Welcome to the Atlassian Community! Unfortunately, no. See this feature request to vote for and follow it. https://jira.atlassian.com/browse/JSWCLOUD-17631

But can you tell me the exact type that Jira calls it? 

Okay, that's a different error. What exact type of field is customfield_10155?

Same error? 

Hi Simon - What type of project are you using? Team-managed? Company-managed? Jira Work Management? That seems a little strange if it is a Company-managed or JWM project, but see if you can see it in the list of custom fields. Go to Settings > Issues > Custom fields and search for it. 

Ah, looks like I missed one more curly bracket at the very end when I cut and pasted. Ad one more } and a new last line or one beside the very last one and give that a whirl. 

Pretty much yes to everything you have above. For the notifications, they should get one anyway if a comment is added that is not "Internal" meaning only the licensed users can see it. As far as assignments, you might could create an automation rule that sends an email to the reporter, depending on what is captured for…

Hi @RVVR - did you ever get this figured out? 

Hi @Ivan Andrieiev You need to change the filter associated with the board. That is what determines what issues show on it. 

You must be a Jira Administrator to add issue types - not just a project administrator.

Nope, one of the current hazards of Team-managed projects I am afraid.

Hi Troy - Welcome to the Atlassian Community! You need to add a post function to clear the resolution field on the transition from Done back to testing.

El cliente no puede Cambiar por el portal

What type of project is this? Company managed? Team managed? If the latter then there are no board settings. And since declined is a Done status category than those cards disappear from the board after two weeks. That might be what’s happening.

Click on the scheme name to edit it. You can add an issue type there.

Hi Olga - Welcome to the Atlassian Community! If you scroll up, you can click on the Summary menu option. Then you will see Issue Types. 

Hi Sunil, If you never want the field to be seen, you can go to the Field Configuration for that project, search for the field and mark it hidden. Settings > Issues > Field Configurations

Bueno - Puede agregar una condición a la transición para permitir que solo el reportero la cambie.

Also, make sure the new field is on the screen.