Jack Brickey Expert

no, Quick filters will not alter the columns. I have not played with the new feature in JWM to see how it behaves as yet. Again this feature is not there in other Applications. The other option would be to create different boards for the different issue types/Workflows.

hi @Alin Iosa , please note that you will not see subtasks in your backlog. With that said, if you are using a Company Managed Project (CMP) you can set your swimlanes by Stories which will the show subtasks (if any) under the story. If you are in a team managed project then you can use the group by feature in the upper…

Hi @hernan.stamato , it appears that the article you have referenced is for a company managed project. If you are in a team managed project as you have indicated you do not have the same configuration options. What exactly are you attempting to achieve?

Hi @Matt Agnes , welcome to the community. Can you try using parentEpic in (EPV-526, EPV-607) in a quick filter to see if it achieves your goal? You might ignore all the other variables until you get only the stories and subtasks associated with the two epics being displayed. Then add in the other conditions.

@Kai Becker , cool approach/solution. You might want to turn this into a Community Article.

Also, while you may already be aware of the following, I thought I would share it just the same as it might help others that stumble across this post. https://www.atlassian.com/migration/help 

Hi @PARISSE Nicolas , you might be best served by reaching out to Atlassian support for assistance. They may be able to simply change OrgB to your OrgA.

Hi @Joe Yee Fung , Welcome to the community. This is a new feature within JWM projects only. I can't say whether it will show up on other project types or not. Having said this you can use quick filters to display by issuetypes that would equate to workflows. It would be interesting to better understand your use case to…

You can use the import feature to update a cascading list if that is your question. Here's a post that discusses the solution. Importing-into-Cascading-Select-field-Possible? 

In your image there is the Story point estimate. Is that not what you want? I believe it is.

No worries at all @filipa.rodrigues that is why the Community exists, to help each other. so yes, I think Automation is the right path. What date field do you have that presents the start date of the new hire? I can create and share an example automation if you like. However, I recommend you try creating based on my above…

Hi @Praveen , I suggest reaching out to Atlassian support for this. The Community can't adequately answer these questions. I would also fewer you here - https://www.atlassian.com/trust/security/advisories 

Hi @Paula Francis , to be clear what do you mean by "subscription "? Are you referring to a filter subscription or maybe an app? If you are an Org admin you can remove any app that was added. If we are dealing with a subscription you can delete the shared filter under admin>system >shared filters

Hi @엄성렬SA , what are you trying to sum? Also I'm not sure I understand the reference to Confluence. Please provide more details on your use case and requirements.

Hi @filipa.rodrigues , I don't quite understand how JQL comes into play here. It seems to me that if you are creating an issue in Jira for onboarding then the creation of the issue could result in Teams notification. Can you explain in more detail your scenario here? Maybe you need a notification "x days" before the new…

Hi @Vara Prasad , have you seen this posts. Not precisely your use case but close. When-Date-picker-field-modified-make-comment-required 

Hi @Umar Maroof , I may be getting a bit confused by your use case however, I don't think the details really would change my answer here. I believe that you should be able to achieve your goal with Automation, or at least this is where I would start. Are you familiar with writing automation rules? Have you attempted this…

Hi @zahavit simhayev , welcome to the community. I assume that you are using a checklist add-on is that correct? I don't believe that is going to be possible to achieve your goal. However, I would reach out to the vendor of the add-on and inquire to be sure.

Hi Dan, natively JQL does not allow you to compare dates. However, depending on your requirements, you might consider using automation. You were basically set up a scheduled rule to run daily. You would use a condition to compare the dates and as an action, you could send an email notification. Further, the email…

Hi @hernan.stamato , Welcome to the community. Would you mind sharing a bit more detail. Could you indicate if this is a team or company manage project by looking in the bottom left? Better yet if you could provide a screenshot of what you were saying and where you are trying to access, the board configurations would be…

Unfortunately no. Previously the menu that you highlighted was in the sidebar where it is for JSW an JSM. I wish it was still the case for JWM. ☹️

Yep that is the best approach until Team matures IMO.

Hi @michelle.purcell , While I have not attempted to use the Team field in any automation it is my understanding that it is not supported. A quick check of JAC which seem to validate that - https://jira.atlassian.com/browse/AUTO-525 .

no. the post is there now

You cannot export history activity via CSV. Please see this open issue - JRACLOUD-38896 - Allow export of JIRA issue details into Excel . Given the age of the issue I would not hold much hope but you never know. There are addons that will allow you to capture this. You could also consider using the APIs. Also, while I do…

Ah...so you are likely using Team Managed Project which does not allow for this. Company managed does as shown below. Again, using "task", "Bug", "improvement" as subtasks will get confusing when you have them as both Task level and Subtask level issuetypes (opinion).

Hi @shankara vijayendran , consider using Automation smartvalue as below. You can use mediumtime possibly? {{[date].[dateformat]}} Takes a date and time that you provide, and returns it in a format of your choosing. This is useful for converting the default output for dates (jiraDateTime), to a format that is easier to…

Please accept answer if it worked for you.

If your "created issues" are know/static for your query then try the following. Replace the issueX issueLink in (issue1, issue2, issue3, issue4)

You can certainly create different sub-task Issuetypes with different names. However, might I suggest a different approach? You could create a custom field that qualified the type of sub task. You could make it a required field when adding a Sub-task. IMO this presents a cleaner solution since traditionally the list of…