Comments
-
Hi @Xena.Olsen , My guess is the EU one, but it might make sense to simply download both in the chance calls come from either.
-
Hi @Glenn A , This should still be possible with an automation like this one below: WHEN: Manual trigger IF: (option) Issue type = Epic THEN: Clone to JPD project (as idea), and link the two through: * is implemented by = Trigger issue ^ This link-type is the connect between ideas and deliveries, so the Jira issue will…
-
I may have figured this out after consulting with my team, but did want to share this publicly with the Community as I have not been able to find much about it. Instead of using the ID found through the API, you can find the project role value needed for this workflow property through inspecting the page / reviewing the…
-
Hi @Felix Liu , Thank you for sharing! Very helpful. Last question from my end - where did you find the projectrole ID value? Is this a user's ID, a group's ID, and/or an actual project role ID? I see in the workflow properties documentation, specifically under a similar example, it uses "2" as the value which I'm unsure…
-
Hi @Felix Liu , That is good to know! Did you use the suggestion @Jeny Stoeva provided above, or go through the workflow properties of the JPD Workflow tab? Could you possibly provide a screenshot of your settings? I've personally been unable to configure this after lots of testing so I'm very curious.
-
Hi @Felix Liu , I believe some/most workflow properties are deprecated or unsupported - including the use case you shared above :( We also understand 1) the documentation should reflect this, and 2) if these features are unsupported then they should not be offered within a JPD project's workflow. Unfortunately this second…
-
Hi @Sue Hannan , It's my understanding when a JPD idea is linked to a Jira issue, you want to copy the Jira issue's single-select field into the JPD idea's single-select field. If there is more to this use case like if this is through deliveries or something else, please share whenever you have the chance. One issue I…
-
Hi @Lisa Kostyshak , The Premium plan is still in EA, and not quite GA yet. We're hoping it's GA soon, but still a bit to be determined - so no firm ETA at the moment.
-
Hi @Hariharan Y , As @Christopher Jaksch mentioned, the Premium plan will have more functionality to restricting views. Having said that, I think it's important to mention a user can qualify as a contributor if they meet one of the following criteria: * Have product access to Jira, Jira Service Management and/or Jira Work…
-
Hi @Miroslav Kralik , Take a look my suggestion on this other JPD Community Question, which provides an automation to calculate the date differential, and enter it into a number-field.
-
Hi @Melorie Acevedo , Thank you for clarifying. JPD does not really offer something like this currently within a field. But I do think the closest thing would be deliveries. Having said that, it might only work if each impacted team has their own Jira project, or if all teams manage their issues within the same Jira…
-
Hi @Melorie Acevedo , Not entirely sure I understand the ask here, or what you might be referring to as "nested questions." Are the efforts (Testing only, discovery, defect resolution, development) the nested questions? Are you hoping that when the impacted team / business unit field is selected, a "child" field then…
-
Hi @aazzopardi , The fields shown during idea creation are related to the view selected under the Customize the idea creation form, along the fields also selected within the same view selected. For example with this view, it has these fields selected: And when this view is selected in the Customize the idea creation form,…
-
Hi @PMSupport , Unfortunately JPD date-fields do not support years at this time. As you've discovered, they are only represented by days, months or quarters at this time. Closest thing I can think of would be to represent a 'Financial Year' through two date-fields. You could then create a timeline view for each 'Financial…
-
Hi @Smita , I don't believe this is possible within any Jira product, and each needs to be added one-by-one. I also don't believe it's possible to do in bulk either. Closest thing I can think of is using the External System Import to update an idea, which can add multiple links, along with update the idea's fields as long…
-
Hi @Ravi , Thank you for sharing that information. In that case, these stakeholders would need to be creators (licensed users) in order to complete those tasks. Deliveries can be created in JWM as well though. There is no limitation here. And when it comes to Confluence, it does compliment JPD. Take a look into this other…
-
Hi @Ravi , Based on what you shared, I'm not entirely sure deliveries are needed. Creating deliveries is also a creator permission, so contributors will not be able to perform this action. Deliveries are typically created after an idea is validated, and not for the "during" / investigation stage of the idea. Contributors…
-
Hi @Erika Lehmann , You may need to also add them as a creator under the project's Access tab as well - depending on the project's access level. You can add this user individually/assign them the creator role, or add the JPD users group as a whole/assign it the creator role.
-
Hi RSavage@stellarindustrial.com , An automation like that is certainly possible. Could be as simple as something like this: ^ Basically any time a comment is added, the idea would be transitioned into the "Comment Review" status, but the status selected in your automation could adhere to your workflow. You could then…
-
Hi @flmonteiro , We may need additional clarification of the workflow, but it sounds like: Issue A is created. An automation then creates Issue B / links the two issues together. The automation also copies the value of a field from Issue A to Issue B. Is that correct? If no - please provide more information if possible. As…
-
Hi @Levi Palmer , I can't seem to replicate this behavior after requiring fields within a Jira project the delivery is being created in. I did notice it took a few moments for the delivery to link which is a bit odd, but again - the ticket did appear in the Delivery tab of the idea after. It might be worth reaching out to…
-
Hi @Kresimir Linke , No I don't believe you are missing anything. As you mentioned, the "Pinned fields" appear in the top section of an idea's right panel. Following that will be the "Fields in this view" section. And finally, there's the "Available fields" section. Each section will "save" if collapsed and/or expanded…
-
Hi @Wilma Winkelmann , This functionality does not exist within JPD at this time. Nor do I believe the ability for stakeholders to create and/or comment on ideas will be on the product roadmap any time soon. Users need to exist within your site in order to do either - which if I'm not mistaken - follows the permission of…
-
Hi @Kevin Rigard , Yes it should be possible, but I guess it just depends on what field-type you are mapping to, and the use case. Feel free to share more about this, and maybe we can provide some suggestions. Check out this page as well on how to find your JPD field's ID.
-
Hi @Ravi , All of that should be possible via automation, but I feel like you might reach your limits rather quickly - especially if the automations will be responsible for creating multiple Confluence pages / deliveries at once. Most of these tasks are typically done manually for validation purposes anyways. Regardless,…
-
Hi @Ravi , I believe ideas are only specific to JPD - so in order for an automation to work as expected, you'd need to create an issue-type that can be mapped to from JPD to JWM. Again, I don't believe ideas can be selected under Jira, JSM, JWM projects at this time.
-
Hi @Amy Fisher , You should be able to add that within the Global fields tab when editing the field!
-
Hi @Eduardo Calvillo , Thank you for the clarification. I'll share this feedback internally with engineering and product. In the meantime, you should be able to map the Original Estimate back to a JPD field using an automation as I previously mentioned! Although the Original Estimate field does not appear selectable in…
-
Hi @Eduardo Calvillo , Are you trying to calculate the work log / time on Jira issues and/or epics that are linked as deliveries on an idea? Or something else? I guess I'm not very familiar with time estimates so any additional clarification may help! There might be a workaround through an automation.
-
Hi @Andy Betts , Not sure if/when vote fields will be supported with Published views, but I'll get this feedback shared with engineering and product. Can't really think of a workaround either since vote fields are not support with automations either :/ Maybe using another field to represent the total votes such as a number…