Gary Spross Community Champion

Our JPD projects are product (not customer) centric. We have around 20 of them. We came up with "standardizations" to the workflow and utilize Global fields were applicable. We have a set of "standardized" views. We also limited the amount of users that are in the "Administrators" role within each of the projects. That…

You can embed your views into Confluence, but they would be separate, individual per project views. The ability to create cross-project views is something Atlassian is providing in the Premium version of Product Discovery. https://www.atlassian.com/software/jira/product-discovery/premium

I do agree that Content Manager has had many improvements. A few additional improvements I'd like to see them make to it are: * Ability to sort by column * Ability to filter by date on specific columns * Ability to export * Ability to Expand/Collapse all That said, I was looking for an automated way to perform this…

Thanks @Levente Szabo _Midori_. At this time we are attempting a workaround, without an add-on, using what's available to us. If we are unsuccessful, I will look into your app.

Thanks @Matthew_Christiansen_Adaptavist. At this time we are attempting a workaround, without an add-on, using what's available to us. If we are unsuccessful I will reach out to learn more about your app.

"Panorama will display Last Viewed data that go way back than one year and will show you what restrictions are applied on the page." It baffles me that a 3rd party app can gather that data, yet Atlassian themselves don't provide a way (that I can find or that Support has informed me of) for users to gather it themselves.…

Thanks for the suggestions @Jim Knepley - ReleaseTEAM. I was trying to avoid having to go down the path of basically creating my own app. We also don't have Rovo at the moment. Can't get past the cost associated with that...

Seems like it would be a "quick fix" for Atlassian. The framework already exists for TMP's in Jira & JSM. Implementing this would be one less issue for customers to have to worry about.

@Nick Haller , sorry, I didn't mean for the customer to have to add the A4J user to the JPD projects. I meant for Atlassian to include the A4J user (or the permission "Project Role (atlassian-addons-project-access)") to the backend JPD project permissions. However it's currently configured for Jira or JSM Team-managed…

@Nick Haller , Could the fix not be to just add the "Automation For Jira" account into JPD. same as it is in place for Jira & JSM, even Team-managed projects of those products?

@Vyshnavi S , it's been suggested to me to utilize the "Advanced fields" section of the edit issue component, specifying the field by it's custom field identifier, as opposed to selecting the field from the drop down. This is necessary because fields created within this project are unique to the project (as you already…

Navigate to "Features" -> "Create ideas" within the project settings and ensure the "Allow contributors to create ideas" toggle is switched on.

Please don't use "Task". That is already an issue type. If the point of implementing a change here is to avoid misunderstandings/confusions, conflating the terminology with something else is not going to help. I'm also not a fan of making this a completely customizable thing. I appreciate that there is some common…

When will this begin rolling out?

@John Bright , It sounds like the "Creator" role in your project has the "Administer projects" permissions. To check this, click the "Manage roles" button (on the access page in the project settings) and select the "Creator" role (just click the role (don't click the little "duplicate" symbol to the right). If you're using…

@John Bright, "Administrators", like "Creators", would need to be licensed to JPD. This is because of the abilities they would be provided within the project. By default, the "Administrators" role has the following elevated permissions (beyond the "Creators" role): * Administer project* This setting provides access to the…

Install the GitLab add-on and configure it. This wouldn't be for JPD, but that's how you would integrate GitLab (similarly to GitHub) with Jira.

Hey @Mikko Silvonen, an easy way to implement what you're looking to do would be to make the access for the projects private (like @Tanguy Crusson mentioned) and then add your group(s) with Jira (not JSM) product access to the projects in the Contributors role.

If you have "Linked Issues" on the "Create" dialog for the issue type (Epic) you are creating in the development project (Commercial Product), you can just add "Linked Issues" in the issue create component as opposed to having to do a branch. Example: If you don't have "Linked Issues" on the "Create" dialog (and don't want…

You should be able to add the link either way, it doesn't matter. Linking an issue with the implements link type connects the issues. For Ideas in JPD projects, this link type shows those tickets in the Delivery section. Did you try refreshing the Idea ticket? It should show the delivery Epic ticket in the Delivery section.

In the create issue component, add the issue link type: implements to the trigger issue.

I agree it's inefficient and cumbersome to have to configure it this way. It's a glaring reason Team-managed projects are more of pain point than any benefit they may provide. I really wish Atlassian would provide JPD in a Company-managed style. It would avoid a lot of these headaches. I'm saying this from a customer…

Don't select "Copy From Trigger Issue". Instead, explicitly select the "Done" status. Try that first and see if it works. If it does, then you will need to include if conditionals to transition to "In Progress" or "Done" based on the status the delivery ticket was transitioned into.

@Jeny Stoeva , I don't disagree that what you state could be the problem, but I'm thinking it's more likely that @Glenn A is attempting a transition to a status that can't be transitioned to based on the configuration of the projects workflow. In this case, he would encounter the "Destination status could not be resolved"…

@Jeny Stoeva, I was thinking that initially as well, but I don't think statuses are impacted by the issue of the projects being of the Team-managed style (and therefore being duplicated in the select list). I say this because I have the same status name utilized in several JPD projects and Company-managed projects, yet I…

@Glenn A , here's a video of Atlassian walking through the creation of an automation rule that transitions an Idea when a linked (via the "Implements" link type) is transitioned. The "Some errors" indicating "Destination status could not be resolved" usually indicates that you are trying to transition to a status that is…

You would need to be accessing the global administration for automation rules to be able to access both projects for scoping the automation rule. This would require you to be a Jira administrator.

@Mickael Maujean , what @Amanda Barber said. JPD is a separate product, so it is billed separately, therefore it can have different user tiers. It's not like an add-on where you're forced to pay for the number of Jira users in your instance even though only a subset may utilize it.

@Clare Lawson, currently, Team-managed projects only allow you to add "standard" issue types. See this post: https://community.atlassian.com/t5/Jira-questions/I-am-trying-to-add-a-sub-task-issue-type-to-my-team-managed/qaq-p/1892862. I just checked within my instance and, as far as I can tell, this is still the case.

Just my 2 cents here, but I would think that's more of a historical log of who has "visited" that view. Just because access was removed from a user doesn't change the fact that they "visited" that view at some point in the past when they did have access. I'm not sure how long the log is kept, so maybe at some point, when…