Jack Brickey Expert

Those are separate activities. While they may have similar names they don’t have the same result. You will have to have separate issues. If this is something that occurs often then consider automation. Such as, when I create an epic with a certain title I create all the stories underneath.

You can leverage the “filter” JQL function. example company filter - project = 123 and company = acme then... filter = company and parentepic = aaa

I’m not sure why you would do that but you can’t have the same issue in two sprints. You can close the issue and have the new issue in the second sprint. 

There are times that the agent creating the linked issue will copy the attachment over if they feel it is critical info but not required. certainly the agent could enter the organization into a text based or select custom field when creating the linked issue. if you want to automate this then consider an automation addon…

I have seen something like this recently but it disappeared. i wonder if this is a browser/cache issue? if you open in different browser what do you see?

My team lives comfortably with the solution you convey here. The JSW users are collaborators and can access on all comments and attachments in the JSD issue. They can place comments there or you can use an automation addon to add comments and transition issues based upon the JSW transitions. 

It appears you are on Cloud I’m which case you cannot access. 

Queues are simply queries of issues so you can easily have issues appear in multiple queues or, thru some field condition have it move between queues. For example, you might have it appear in the “team A” queue if it is assigned to a member of a group called team-A and then by reassigning to a member in the team-b group…

Hi Javad, so are you saying that this is not happening if a participant is commenting? It may be that you have an automation that specifically has a reopen condition when the comment is added by the reporter. Please review your automation rules and feel free to share them here if the answer is not obvious. 

The way it is written, yes the results will not include issues w/ FV empty. If you want something to show up when the FV is empty then you should add "...OR fixversion is Empty...". This is often forgotten when constructing JQLs.

Great article! This really pulls together some great data new and old and will certainly benefit many in the Community. Congrats on your first article!

Are you talking Jira Software here or Jira Service Desk? I ask as this is posted in Jira not JSD but you mention agents. if the user sending in an email is a customer of the project it should be a public comment. If they are an internal JSW user collaborating on JSD issue, I.e. not agents it will be internal. 

So if you want the user to update the time tracking at each transition of the WF then you can add a Field modified Validation on each transition except the Create and require Time Spent. You do not want to make the field required as it will be required on Create too as you have found.

While you can add a custom field to the form that is used when creating an issue you cannot add the custom field in the detail view of and issue.

yes it is possible. See if this article helps migrate-between-next-gen-and-classic-projects 

try this... 1) add a Field has been modified validation to the transition from In Dev to In QA for the Assignee field 2) use the jira.permission.assignable.group property key on the In Dev status and have a group defined that has the QA users included FWIW...here is a thread where I learned about #2 -…

Hi Shannon, I'm unclear why you cannot achieve your goal by simply using the Component itself. You could create a filter for each product manager based upon component. You could further associate these filters to a Dashboard for each PM. There is not a field for component lead that could be leveraged w/in a JQL.

There is not inherient issue w/ sharing workflows across projects and in fact can make things much easier to maintain. With that said, it can be rather limiting since many projects/teams don't work the exact same way as other teams. I would not be surprised that trying to maintain a single workflow across 114 projects…

the way NG works is that w/in the Backlog view you have a "Backlog" and a "Board" section. if you wish them to appear on the board you drag them to that section. Once that is done they should appear in the proper column.

Agree with Jakub. Below is what I see. Where are you logging work from?

@Kelvin A Hill, regarding your idea on a central thread. One thing I found useful, and still do, is that Atlassian created a parent issue in JAC for all issues related to the "new issue view" (JRACLOUD-70555 ). This allowed me to more readily find the latest list of issues and status by simply remembering one issue. I…

yes indeed and it is actually better than that. The way JSD is priced is that you pay only for Agents (those users that will be assigned JSD issues to resolve). Then you can have the rest of your team be Customers which are free. Customers can open issues by email or via a customer Portal. All issues go into Queues that…

Atlassian may be able to change your domain for you when ready to do so. They allow you to do this once with your cloud instance. Reach out to Atlassian Support. 

For the issue to be created in the backlog the initial status (at creation) needs to be the same as what defines your backlog. It seems you have a status called Backlog and your board is defined by issues in the To Do status. Further it seems your initial status is Backlog. Assuming this is correct and if you don’t need…

Yep if you have multiple labels it will not work. You would need an addon like EasyBi I think or export to Excel and post process.

You can create a dashboard and use a pie chart by labels. However if you have a lot of labels it will become unwieldy.

@Hana , it appears Nic has landed on the root cause. You will need to ensure “Done” is in right-most column if indeed you consider it complete.

this is a very unique use case and TBH I don't know how best to approach it. Maybe an addon. However, if it were me I would not attempt to achieve in this manner. Rather I would use Epics w/in a project and use something like Automation for Jira or similar. When the Epic transitions into some status A4J would create all…

@carolyn french, you won!! ;-)

where do you want the shortcut to appear? you can add a shortcut in the sidebar of the project.