![]() You can also copy an issue under a feature by holding down the ctrl or cmd key, then it will create the new link without breaking the 'old' one.Īs for ranking a structure by rank, you can add an explicit rule to sort by rank to include it. Since under the hood an Agile board is based off a JQL query, maybe it makes sense to build a new structure, based off that same query, and then when you run your grouping and extend rules you should be having a little more success.Īs to moving items under features removing the epic link, that's expected behavior if you move an item (since by definition it removes it at the source). There are certain limitations to the way issues on a board behave that Structure doesn't circumvent (nor should it). You're experiencing exactly this because your structure is tied to an Agile board in Jira. Sorry to hear you've run into some issues here. It's very close to working but there are some signficant design flaws. Long story short, Structure has some fundamental problems that are causing us frustration as end users. This is very disappointing due to the issues I mentioned above. Only structures based on boards allow this functionality. It's not obvious from the documentation or brochureware but Structure will not allow you to use Rank to re-sort Structures based on JQL queries. We're working on building in some automation to correct it after the fact but it's extra work for the system and doesn't make a lot of sense.Ĥ. This invalidates tons of planning in Jira and makes our Epics unreliable. If I create an agile board structure, display Epics, and extend Features into it via linking then when I move a Story from under an Epic to under a Feature, it blanks out the Epic Link field. This is extremely critical and invalidates the entire board structure for my product managers.ģ. If I create an agile board structure and display Epics then it will always exclude any tickets that don't have Epics already since there's no "No Epic" grouping. Instead they've introduced all sorts of whacko functionality around this and it's causing us tons of headaches.Ģ. Why in the world would it be designed this way?!?! It should just have an option to "Display Epics as tickets". Structure forces you to choose to display Epics (without normal tickets) OR tickets (excluding epics) but won't allow you to have a complete list of everything. There are several disadvantages to the way Structure treats this situation:ġ. We're trying to do Epic->Feature->Story as well and are currently using a Structure based on a board to insert the Epics which is then extended by links to Feature and then Story.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |