Dave Mathijs Community Champion

No, reporting is quite limited (to say non-existing) in Assets yet. Alternatively - but that would be duplicate work in my opinion - you could create a Jira project where each issue represents a hardware asset that corresponds to the object. Then create a workflow that represents the statuses and report on the statuses…

When you add the user to the Dev Team project roles, does it resolve the issue?

You cannot track additional information in a status, but you can always add a Comment on the Activity tab of the object itself.

Hi @María José Villanueva Welcome to the Atlassian Community! Great to hear that you're studying for the ACP-620 exam. Is the DEV Team project actually a team-managed project?

Hi @Roman Zolotarevskyi Are you able to add a timeline by selecting a period on the timeline itself? Please note that only the field Start date and Due date can be used and need to be added to the issue view (screens).

Hi @Angela Honegger You can use Statuses in your Object Schema to create statuses for each life cycle state of your assets. What is a status?

Hi @Sayali Zalse In that case: Use your kanban backlog

Hi @Reynaldo Kevin Darmawan Welcome to the Atlassian Community! You can read all info about it here: Embed a widget onto a web page Spoiler: It's rather limited. So, to answer your questions: No.

Hello @hpuc That's by design. When you publish a page, you're no longer editing it, so it starts at the top because it refreshes the page.

Hi @Missy Strickland Releasing via a Kanban board in a company-managed project In a Kanban project, releasing a version via the board will release all issues in that version that are 'Done' (i.e. in the right-most column of the board). * Go to the project that your version is in. * Click Kanban board. * Click the Release…

Hi @Emilee It seems I can create an article rather than a discussion. Can you transform it into a discussion so I am eligible for the badge?

@Vicki In addition to what @John Funk said, also create a post function for each 'to do' (grey) and 'in progress' (blue) status that clears the resolution. Otherwise you'll end up with resolved issues in a non-resolved status (if they are re-opened)

@Leslie Hicks Check with the user who make the comment if it's actually made from the portal? Chances are this is a user with a JSM license (agent), not a portal-only customer.

When I think of a theatre, it's definitely a movie theatre. For my earliest memory, movie theater Trioscoop in Hasselt, Belgium comes to mind, the place where I went to see my first movie, E.T. the Extra-Terrestrial at the age of 9

I loved the Roadmap feature, now I love the Timeline feature. 😉

Hi, You have a site-wide setting to allow users to select a status for an issue they're creating. (See Settings -> System -> Edit Settings -> Options -> Status -> On/Off) For the moment, you cannot limit the available statuses when this is set to "On". It all depends on your workflow and conditions you might have set to…

Hi @Greg Jordan The list of JQL queries in unexhaustive, so creating a comprehensive list would be impossible. Besides, it also depends the custom fields you might have created for your site. I suggest to start with this documentation article: Use advanced search with Jira Query Language (JQL) and have a look at the…

You should let the system mark handled mails as read and refrain from changing the read/unread status manuallly. However, If you want to stop the repeated ticket creation for that specific mail, you should mark it as read manually (by exception)

Jira will mark handled mails as read. Jira will handle unread mails as new mails and generate a new ticket. So handled mails should not be set to unread again (manually).

Hi @Tom Mina-Coull , did someone (who has access to the mailbox) manually set this e-mail from read to unread?

Hi @Anne Jang Is this change effective for issue type hierarchy both above AND below Epic level? * Parent link between Epic and the Initative level (above Epic level) Example: Initiative -> Epic (parent -> child) * Parent link between Epic and the issues within the Epic (below Epic level) Example: Epic -> Task/Story/....…

Personally, I don't like it when people call me 'David' or 'Davy', just call me 'Dave'. Every once in a while people call me 'Mathijs' because it is a more common first name in The Netherlands.

Hi @Blair Yes, you are correct. Jira Software only has a "back-end" so all users need a license Jira Service Management has a "front-end" (the customer-facing portal) where users don't need a license. The "back-end" of Jira Service Management is for agents who handle the customer's requests. They do need a license. In both…

Hi @Soundarya Rangarajan This support articles provided you some things to keep in mind when migrating the project type: Migrate between team-managed and company-managed projects

Thanks for sharing @Finch Grace 

@joe vee tew Please click the green 'Accept answer' button if it answered your question.

JJ is super cute! 🐶

@Lena Sargsyan Like the error message says, check the incompatible field configuration(s) or workflows associations. If Status A is available for issue type X, but not for issue type Y, then you won't be able to change the issue type in bulk.

Hi @joe vee tew welcome to the Atlassian Community! Here's the link to the documentation: Invite guests for external collaboration The feature is still in beta. Guests are free of charge (up to 5 guests per paid user). Note: Total paid and guest users cannot exceed the current Confluence site user limit.

Can you please show what is mentioned as help text under Change Issue Type? It is now blocked by clicking on the selection list.